Skip to content

IO FinNet tss-lib vulnerable to timing attack from non-constant time scalar multiplication

Critical severity GitHub Reviewed Published Apr 21, 2023 to the GitHub Advisory Database • Updated Feb 5, 2025

Package

gomod github.com/binance-chain/tss-lib (Go)

Affected versions

< 2.0.0

Patched versions

2.0.0
gomod github.com/bnb-chain/tss-lib (Go)
< 2.0.0
2.0.0

Description

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

References

Published by the National Vulnerability Database Apr 21, 2023
Published to the GitHub Advisory Database Apr 21, 2023
Reviewed Feb 5, 2025
Last updated Feb 5, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(48th percentile)

Weaknesses

CVE ID

CVE-2023-26556

GHSA ID

GHSA-3w84-4mjc-rjw7

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.