This page lists publicly disclosed CVE vulnerabilities affecting iofinnet tss-lib (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2023-26557 | io.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.) | [email protected] | 7.5 | 0.27% | 2023-04-21 | 2025-02-05 |
| CVE-2023-26556 | io.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.) | [email protected] | 9.1 | 0.56% | 2023-04-21 | 2025-02-05 |
| CVE-2022-47930 | An 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. | [email protected] | 6.8 | 0.06% | 2023-04-21 | 2025-02-05 |
| CVE-2022-47931 | IO FinNet tss-lib before 2.0.0 allows a collision of hash values. | [email protected] | 9.1 | 0.19% | 2022-12-23 | 2025-04-15 |