# CVE-2011-4574: Weak cryptography in PolarSSL

> PolarSSL's random number generation relies on a virtualizable timer, leading to predictable keys in virtualized environments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2021
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-69cr-qg65-xgm7

## What is CVE-2011-4574?

CVE-2011-4574 is a critical vulnerability in PolarSSL, published on 27 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2011-4574?

It affects 1 product.


Products: Polarssl Polarssl.

## How do I fix CVE-2011-4574?

No fix has been published for CVE-2011-4574 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-4574 being exploited?

There is no known exploitation of CVE-2011-4574 in the wild and no public exploit code.

## Other vulnerabilities in PolarSSL

- [CVE-2014-8628](https://insights.sbomify.com/CVE-2014-8628/): Denial of service in n/a (high 7.8)
- [CVE-2013-5914](https://insights.sbomify.com/CVE-2013-5914/): Buffer overflow in the ssl_read_record function in ssl_tls.c in PolarSSL before 1.1.8, when using TLS 1.1, might allow remote attackers to e (medium 6.8)
- [CVE-2014-8627](https://insights.sbomify.com/CVE-2014-8627/): Security feature bypass in n/a (medium 5.0)
- [CVE-2013-5915](https://insights.sbomify.com/CVE-2013-5915/): Information disclosure in n/a (medium 4.3)
- [CVE-2013-4623](https://insights.sbomify.com/CVE-2013-4623/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4574 and fix it if it is affected.

What it is: CVE-2011-4574 is a critical vulnerability in PolarSSL, published on 27 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4574 in the wild and no public exploit code.

Affected product: PolarSSL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-4574/ (Markdown: https://insights.sbomify.com/CVE-2011-4574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4574
- OSV: https://osv.dev/vulnerability/CVE-2011-4574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-4574/
Summaries are generated and may contain mistakes; the official description above is the record.