SSH communication decryption via predictable X25519 keys
Published May 31, 2022 · Updated Apr 22, 2025
Weak key generation in SSH.NET 2020.0.0 through 2020.0.1 allows attackers to decrypt SSH communications by observing X25519 exchanges. KeyExchangeECCurve25519.Start fills the X25519 client private key with bytes from System.Random, whose default seed derives from the millisecond system tick count. Exploitation requires observation of an X25519 handshake and brute-forcing that seed; the demonstrated consequence is disclosure of the protected SSH session, not modification or interruption.
Summary
What happened
Weak key generation in SSH.NET 2020.0.0 through 2020.0.1 allows attackers to decrypt SSH communications by observing X25519 exchanges. KeyExchangeECCurve25519.Start fills the X25519 client private key with bytes from System.Random, whose default seed derives from the millisecond system tick count. Exploitation requires observation of an X25519 handshake and brute-forcing that seed; the demonstrated consequence is disclosure of the protected SSH session, not modification or interruption.
The record
- CVE
- CVE-2022-29245
- Published
- May 31, 2022
- Updated
- Apr 22, 2025
- Vendor
- SSH.NET
- Product
- SSH.NET
- Classifications
- CWE-338, CWE-330, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=>= 2020.0.0, < 2020.0.2
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
- X25519 seed brute-force 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