CVE-2001-0950 json
ValiCert Enterprise Validation Authority (EVA) Administration Server 3.3 through 4.2.1 uses insufficiently random data to (1) generate sess…
published 2001-12-04 24 y ago modified 2026-06-16 4 mo ago also EUVD-2001-0933
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
ValiCert Enterprise Validation Authority (EVA) Administration Server 3.3 through 4.2.1 uses insufficiently random data to (1) generate session tokens for HSMs using the C rand function, or (2) generate certificates or keys using /dev/urandom instead of another source which blocks when the entropy pool is low, which could make it easier for local or remote attackers to steal tokens or certificates via brute force guessing.
Patch / fix
- securityfocus.com/bid/3620 advisory
- securityfocus.com/bid/3618 advisory
Exploit prediction
1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- marc.info http://marc.info/?l=bugtraq&m=100749428517090&w=2 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-331 Insufficient Entropy
References
-
securityfocus.com
/bid/3620
vdb-entry, broken-link, patch, third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/3618
vdb-entry, broken-link, patch, third-party-advisory, vendor-advisory
-
marc.info
/?l=bugtraq&m=100749428517090&w=2
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/7651
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/7653
vdb-entry, third-party-advisory
-
valicert.com
/support/security_advisory_eva.html
broken-link
Sources
- CVE List CVE-2001-0950
- NVD CVE-2001-0950
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.