LiveActive security incident?Get immediate response
CVE Record

CVE-2006-3419: Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically stron...

Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically strong RAND_bytes, and seeds the entropy value at start-up with 160-bit chunks without reseeding, which makes it easier for attackers to conduct brute force guessing attacks.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older Tor releases before 0.1.1.20 used weaker OpenSSL pseudo-random output and did not reseed after startup. That could make some cryptographic values easier to guess by brute force. The sources do not provide CVSS, confirmed exploitation, or detailed impact beyond easier guessing attacks. Exposure appears limited to systems still running Tor versions before 0.1.1.20, including legacy packaged deployments. The source bundle does not identify affected CPEs, operating systems, or downstream products. Treat this as a legacy exposure check, not an emergency, unless the organization still operates old Tor infrastructure. Lack of CVSS and exploitation evidence lowers urgency, but cryptographic weaknesses in anonymity software deserve prompt removal when found. Mitigation focus: Upgrade Tor to 0.1.1.20 or later where legacy versions are found.; Review Gentoo GLSA-200606-04 if using historical Gentoo packages.; Check current Tor vendor guidance for supported upgrade paths..

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-2006-3419 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.