Key retrieval via predictable HAVEGE output
Published Oct 27, 2021 · Updated Aug 7, 2024
Weak random generation in Mbed TLS before 1.1.0 allows remote attackers to retrieve keys in affected virtualized environments. The PolarSSL HAVEGE generator relies solely on processor timing from RDTSC, so hosts that disable or impair the instruction supply zeros or predictable values that make its output predictable. Only virtualized instances with a disabled or handicapped RDTSC call are affected; nonvirtualized instances are excluded, and the documented consequence is key retrieval.
Summary
What happened
Weak random generation in Mbed TLS before 1.1.0 allows remote attackers to retrieve keys in affected virtualized environments. The PolarSSL HAVEGE generator relies solely on processor timing from RDTSC, so hosts that disable or impair the instruction supply zeros or predictable values that make its output predictable. Only virtualized instances with a disabled or handicapped RDTSC call are affected; nonvirtualized instances are excluded, and the documented consequence is key retrieval.
The record
- CVE
- CVE-2011-4574
- Published
- Oct 27, 2021
- Updated
- Aug 7, 2024
- Vendor
- Mbed TLS
- Product
- Mbed TLS
- Classifications
- CWE-338
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=PolarSSL 1.1.0
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
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