LiveActive security incident?Get immediate response
CVE Record

CVE-2001-0950: ValiCert Enterprise Validation Authority (EVA) Administration Server 3.3 through 4.2.1 uses insufficiently...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This old ValiCert EVA Administration Server flaw concerns weak randomness used for session tokens and certificate or key generation. In a certificate authority environment, weak randomness can undermine trust because tokens, certificates, or keys may become easier to guess. The provided sources do not establish current exploitation or a confirmed patch path. Exposure is likely limited to legacy EVA deployments or environments still trusting certificates or keys generated by affected versions. The bundle does not identify modern product names, CPEs, deployment counts, or internet exposure indicators. Prioritize if EVA remains in use or its generated certificates still anchor business trust. For most organizations, urgency depends on legacy presence rather than broad current exposure. Confirm inventory before committing major remediation effort. Mitigation focus: Inventory for EVA Administration Server 3.3 through 4.2.1.; Check archived ValiCert guidance before applying product-specific changes.; Retire or isolate any affected legacy administration servers..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2001-0950 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.