# CVE-2007-5502: Weak cryptography in n/a

> Weak PRNG in OpenSSL FIPS module allows attackers to predict random data, bypassing security mechanisms relying on randomness.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r3wh-w6m7-m5c3

## What is CVE-2007-5502?

CVE-2007-5502 is a medium-severity vulnerability in n/a, published on 1 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PRNG implementation for the OpenSSL FIPS Object Module 1.1.1 does not perform auto-seeding during the FIPS self-test, which generates random data that is more predictable than expected and makes it easier for attackers to bypass protection mechanisms that rely on the randomness.

Weakness: CWE-310

## Which versions are affected by CVE-2007-5502?

It affects 1 product.


Products: Openssl Fips Object Module.

## How do I fix CVE-2007-5502?

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

## Is CVE-2007-5502 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5502 and fix it if it is affected.

What it is: CVE-2007-5502 is a medium-severity vulnerability in n/a, published on 1 Dec 2007. 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-2007-5502 in the wild and no public exploit code.

Affected product: n/a. 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-2007-5502/ (Markdown: https://insights.sbomify.com/CVE-2007-5502/index.md)
```

## Sources

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

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