Iofinnet Tss Lib vulnerabilities
4 vulnerabilities
Known vulnerabilities in Iofinnet Tss Lib, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
PrioritiseCVE-2023-26557iofinnet · tss-lib +2 moreiofinnet tss-libio.finnet tss-lib before 2.0.0 can leak the lambda value of a private key via a timing side-channel attack because it relies on Go big.Int, which is not constant time for Cmp, modular exponentiation, or modular inverse. An example leak is in crypto/paillier/paillier.go. (bnb-chain/tss-lib and thorchain/tss are also affected.)CVSS7.5HighEPSS0.86%PrioritiseCVE-2023-26556iofinnet · tss-lib +2 moreiofinnet tss-libio.finnet tss-lib before 2.0.0 can leak a secret key via a timing side-channel attack because it relies on the scalar-multiplication implementation in Go crypto/elliptic, which is not constant time (there is an if statement in a loop). One leak is in ecdsa/keygen/round_2.go. (bnb-chain/tss-lib and thorchain/tss are also affected.)CVSS9.1CriticalEPSS0.86%RoutineCVE-2022-47930iofinnet · tss-lib +2 moreiofinnet tss-libAn issue was discovered in IO FinNet tss-lib before 2.0.0. The parameter ssid for defining a session id is not used through the MPC implementation, which makes replaying and spoofing of messages easier. In particular, the Schnorr proof of knowledge implemented in sch.go does not utilize a session id, context, or random nonce in the generation of the challenge. This could allow a malicious user or an eavesdropper to replay a valid proof sent in the past.CVSS6.8MediumEPSS0.52%RoutineCVE-2022-47931iofinnet · tss-lib +2 moreiofinnet tss-libIO FinNet tss-lib before 2.0.0 allows a collision of hash values.CVSS9.1CriticalEPSS0.49%