TLS data exposure via predictable session keys
Published Jul 17, 2023 · Updated Oct 29, 2024
Cryptographic key derivation in wolfSSL 3.14.0 through 5.6.0 allows man-in-the-middle attackers to read or alter TLS 1.3 data. The client handshake accepts a ServerHello containing neither key_share nor pre_shared_key and derives the master secret from a predictable default IKM buffer. Exploitation requires a TLS 1.3 client to connect to a malicious server while traffic is observable; private keys and server-certificate validation remain unaffected.
Summary
What happened
Cryptographic key derivation in wolfSSL 3.14.0 through 5.6.0 allows man-in-the-middle attackers to read or alter TLS 1.3 data. The client handshake accepts a ServerHello containing neither key_share nor pre_shared_key and derives the master secret from a predictable default IKM buffer. Exploitation requires a TLS 1.3 client to connect to a malicious server while traffic is observable; private keys and server-certificate validation remain unaffected.
The record
- CVE
- CVE-2023-3724
- Published
- Jul 17, 2023
- Updated
- Oct 29, 2024
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-20, CWE-295, T1557
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 17, 2023CVE publishedPublication date reported by the CVE source.
- Oct 29, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.14.0 <=5.6.0
What conditions does exploitation require?
What is affected?
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
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