Private-key recovery via 32-bit RNG seeding
Published Sep 18, 2022 · Updated Aug 3, 2024
Weak random-number generation in Profanity 1.60 and earlier allows attackers to recover Ethereum vanity-address private keys. Dispatcher.cpp seeds a 64-bit Mersenne Twister with one unsigned 32-bit random_device result, limiting the initial private-key space to roughly four billion candidates. A signed transaction exposes the public key needed to reverse Profanity's deterministic expansion, letting remote attackers derive the private key and transfer wallet assets.
Summary
What happened
Weak random-number generation in Profanity 1.60 and earlier allows attackers to recover Ethereum vanity-address private keys. Dispatcher.cpp seeds a 64-bit Mersenne Twister with one unsigned 32-bit random_device result, limiting the initial private-key space to roughly four billion candidates. A signed transaction exposes the public key needed to reverse Profanity's deterministic expansion, letting remote attackers derive the private key and transfer wallet assets.
The record
- CVE
- CVE-2022-40769
- Published
- Sep 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-338, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Profanity Brute-forcefunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Profanity-generated wallet theftreported exploitation
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