Private-key recovery via biased P-521 nonces
Published Apr 15, 2024 · Updated Nov 4, 2025
Weak nonce generation in PuTTY 0.68 through 0.80 allows attackers to recover NIST P-521 private keys from about 60 signatures. The P-521 signing path derives each nonce in a way that forces its top nine bits to zero, enabling lattice-based key recovery. Attackers must collect signatures from public signed commits or a rogue SSH server, after which the recovered key permits impersonation wherever it is accepted.
Summary
What happened
Weak nonce generation in PuTTY 0.68 through 0.80 allows attackers to recover NIST P-521 private keys from about 60 signatures. The P-521 signing path derives each nonce in a way that forces its top nine bits to zero, enabling lattice-based key recovery. Attackers must collect signatures from public signed commits or a rogue SSH server, after which the recovered key permits impersonation wherever it is accepted.
The record
- CVE
- CVE-2024-31497
- Published
- Apr 15, 2024
- Updated
- Nov 4, 2025
- Vendor
- PuTTY
- Product
- PuTTY
- Classifications
- CWE-338
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.68 <0.81
What conditions does exploitation require?
What is affected?
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
- CVE-2024-31497 POCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Cal-CSIC active-exploitation reportreported 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