CVE-2007-5502 json
The PRNG implementation for the OpenSSL FIPS Object Module 1.1.1 does not perform auto-seeding during the FIPS self-test, which generates r…
published 2007-12-01 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5477
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- securityfocus.com/bid/26652 patch
- secunia.com/advisories/27859 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-5502 updated
openssl FIPS module PRNG flaw
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
securityfocus.com
/bid/26652
vdb-entry, patch
-
secunia.com
/advisories/27859
third-party-advisory, patch, vendor-advisory
-
vupen.com
/english/advisories/2007/4044
vdb-entry
-
securitytracker.com
/id?1019029
vdb-entry
- openssl.org /news/secadv_20071129.txt
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38796
vdb-entry
-
kb.cert.org
/vuls/id/150249
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2007-5502
- NVD CVE-2007-5502
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.