LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0535: OpenSSL 0.9.4 and OpenSSH for FreeBSD do not properly check for the existence of the /dev/random or /dev/ur...

OpenSSL 0.9.4 and OpenSSH for FreeBSD do not properly check for the existence of the /dev/random or /dev/urandom devices, which are absent on FreeBSD Alpha systems, which causes them to produce weak keys which may be more easily broken.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

On FreeBSD Alpha systems that lacked /dev/random and /dev/urandom, older OpenSSL 0.9.4 and OpenSSH builds did not detect the missing entropy sources and generated cryptographic keys from weak randomness. Keys produced in that environment could be easier for an attacker to guess or reproduce, undermining SSH and TLS trust on affected hosts from that era. Extremely narrow today: FreeBSD Alpha hosts running OpenSSL 0.9.4 or the affected OpenSSH port from 2000. Modern fleets are not exposed, but residual risk exists only if archived keys generated on those systems are still trusted anywhere (backup infrastructure, legacy CAs, embedded devices). Low priority for current operations. Only relevant if the organization still trusts keys or certificates generated on a FreeBSD Alpha system from the 2000 timeframe. Fold into legacy-system decommissioning and key-rotation hygiene rather than emergency patching. Mitigation focus: Apply the FreeBSD-SA-00:25 advisory guidance and upgrade to patched OpenSSL and OpenSSH ports.; Rotate any SSH host keys, user keys, or TLS certificates generated on affected FreeBSD Alpha systems.; Ensure /dev/random and /dev/urandom are present and seeded before generating keys..

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-2000-0535 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
1Source 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.