Private-key recovery via exposed multisignature nonce
Published Jul 19, 2021 · Updated Aug 4, 2024
Cryptographic key disclosure in Xuperchain 3.6.0 allows remote attackers to recover a user's private key from a multisignature. The workflow exposes each signer's nonce in KList, so a proposer holding the matching partial signature can solve sk=(s-k)/H(PK,R,m). Possession of a participant's partial signature and public transaction context is sufficient to derive that participant's P-256 private key.
Summary
What happened
Cryptographic key disclosure in Xuperchain 3.6.0 allows remote attackers to recover a user's private key from a multisignature. The workflow exposes each signer's nonce in KList, so a proposer holding the matching partial signature can solve sk=(s-k)/H(PK,R,m). Possession of a participant's partial signature and public transaction context is sufficient to derive that participant's P-256 private key.
The record
- CVE
- CVE-2020-22741
- Published
- Jul 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-312
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2021CVE 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
- Xuperchain multisignature private-key recovery proof of conceptproof of concept · demonstrated
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