Signing compromise via unproven keygen parameters
Published Apr 23, 2020 · Updated Aug 4, 2024
Cryptographic parameter validation in Binance tss-lib before 1.2.0 allows attackers to compromise signing rounds or read sensitive data. The ECDSA key-generation round accepted participant-supplied h1 and h2 values without proof that they generated the same group modulo N. Attackers must participate in distributed key generation and submit crafted parameters; the bounded effects are signing-round compromise or disclosure from peers.
Summary
What happened
Cryptographic parameter validation in Binance tss-lib before 1.2.0 allows attackers to compromise signing rounds or read sensitive data. The ECDSA key-generation round accepted participant-supplied h1 and h2 values without proof that they generated the same group modulo N. Attackers must participate in distributed key generation and submit crafted parameters; the bounded effects are signing-round compromise or disclosure from peers.
The record
- CVE
- CVE-2020-12118
- Published
- Apr 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo