Unscored severity · published Jan 17, 2014
CVE-2013-7295
Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting on Intel Sandy Bridge and Ivy Bridge platforms, does not properly generate random…
–
CVSS
1.8%
EPSS
No
On KEV
Description
Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting on Intel Sandy Bridge and Ivy Bridge platforms, does not properly generate random numbers for (1) relay identity keys and (2) hidden-service identity keys, which might make it easier for remote attackers to bypass cryptographic protection mechanisms via unspecified vectors.
Exploitation
Is it being used?
Exploit prediction (EPSS)1.8% · higher than 78% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
TO
Tor · Torproject
through 0.2.4.19; 0.2.4.1; 0.2.4.2; 0.2.4.3; 0.2.4.4; 0.2.4.5; +13 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2013-7295
CVE.org
https://www.cve.org/CVERecord?id=CVE-2013-7295
lists.opensuse.org
http://lists.opensuse.org/opensuse-updates/2014-01/msg00095.html
Vendor Advisory
https://lists.torproject.org/pipermail/tor-talk/2013-December/031483.html
More from Tor
7.5
CVE-2016-9079
Mozilla Firefox, Firefox ESR, and Thunderbird Use-After-Free Vulnerability
9.3
CVE-2026-77642
tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest type
9.1
CVE-2026-44603
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007
9.1
CVE-2026-44597
Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in its payload, aka TROVE-2026-011
9.0
CVE-2026-77638
Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle (impersonate) the onion service that the client…