CVE-2006-3419 json
Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically strong RAND_bytes, and seeds the entr…
published 2006-07-07 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3415
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- tor Debian 14, Debian 13, Debian 12 0.1.1.20-1
debian advisories DEBIAN-CVE-2006-3419
- secunia.com/advisories/20514 advisory
Exploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
secunia.com
/advisories/20514
third-party-advisory, patch, vendor-advisory
-
security.gentoo.org
/glsa/glsa-200606-04.xml
vendor-advisory
-
osvdb.org
/25880
vdb-entry
- tor.eff.org /cvs/tor/ChangeLog
Sources
- CVE List CVE-2006-3419
- NVD CVE-2006-3419
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.