CVE-2011-4574: Weak RNG
First published: Wed Oct 27 2021(Updated: )
PolarSSL versions prior to v1.1 use the HAVEGE random number generation algorithm. At its heart, this uses timing information based on the processor's high resolution timer (the RDTSC instruction). This instruction can be virtualized, and some virtual machine hosts have chosen to disable this instruction, returning 0s or predictable results.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PolarSSL | <1.1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2011-4574?
The severity of CVE-2011-4574 is considered moderate due to its impact on random number generation reliability.
Which versions of PolarSSL are affected by CVE-2011-4574?
CVE-2011-4574 affects all versions of PolarSSL prior to v1.1.0.
How do I fix CVE-2011-4574?
To fix CVE-2011-4574, upgrade PolarSSL to version 1.1.0 or later.
What is the main issue with the HAVEGE algorithm in CVE-2011-4574?
The main issue with the HAVEGE algorithm is that it relies on timing information which can be compromised in virtualized environments.
Is CVE-2011-4574 relevant to virtual machine hosts?
Yes, CVE-2011-4574 is particularly relevant to virtual machine hosts where the RDTSC instruction can be disabled.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/softwarecombine
- vendor/polarssl
- canonical/polarssl