VYPR
High severityNVD Advisory· Published Apr 21, 2023· Updated Feb 5, 2025

CVE-2023-26557

CVE-2023-26557

Description

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.)

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

io.finnet tss-lib before 2.0.0 leaks the lambda value of a private key via a timing side-channel attack due to non-constant-time Go big.Int operations.

CVE-2023-26557 describes a timing side-channel vulnerability in io.finnet tss-lib, a threshold signature scheme library, prior to version 2.0.0. The library relies on Go's big.Int for cryptographic operations such as comparison, modular exponentiation, and modular inverse, which are not constant-time. This non-constant-time behavior can leak the lambda value (a private key component) to an attacker capable of measuring operation timings. The affected code is located in crypto/paillier/paillier.go and also impacts forks like bnb-chain/tss-lib and thorchain/tss [1][2].

To exploit this vulnerability, an attacker needs the ability to observe timing variations during cryptographic operations. This could be achieved through local execution on the same system or via network timing analysis if the attacker can trigger operations remotely. No authentication is required beyond the ability to interact with the TSS library [2]. The timing leakage specifically affects the Cmp, modular exponentiation, and modular inverse functions in Go's big.Int package.

Successful exploitation allows an attacker to recover the lambda value, which is a secret share in the threshold signature scheme. This can lead to compromise of the private key, enabling signature forgery and potentially theft of funds or unauthorized transactions in cryptocurrency wallets that use the vulnerable library [2].

The vulnerability is fixed in version 2.0.0 of the library. Users are strongly advised to upgrade to the latest version. The issue is also tracked as GO-2023-1733 in the Go vulnerability database [4]. No workarounds are available; updating the library is the recommended mitigation [1][3].

AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
github.com/bnb-chain/tss-libGo
< 1.3.6-0.20230324145555-bb6fb30bd3eb1.3.6-0.20230324145555-bb6fb30bd3eb
github.com/binance-chain/tss-libGo
< 1.3.6-0.20230324145555-bb6fb30bd3eb1.3.6-0.20230324145555-bb6fb30bd3eb

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.