CVE-2013-7295
Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting...
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.
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2013-7295- CVSS 2.0
- 4.0 Medium
AV:N/AC:H/Au:N/C:P/I:P/A:N - Weakness
- CWE-310
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2013-7295- Updated
- 2026-11-02
EUVDEUVD-2013-7072 No score
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.
- Record
EUVD-2013-7072- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-3x57-m985-pg67 No score
Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting...
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.
- Record
GHSA-3x57-m985-pg67- Updated
- 2026-11-02
OSV No score
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.
- Record
CVE-2013-7295- Updated
- 2026-11-02
OSVDEBIAN-CVE-2013-7295 No score
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.
- Record
DEBIAN-CVE-2013-7295- Updated
- 2026-11-02
OSVMGASA-2014-0059 No score
Updated tor package fixes security vulnerability
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 relay identity keys and hidden-service identity keys, which might make it easier for remote attackers to bypass cryptographic protection mechanisms via unspecified vectors (CVE-2013-7295).
- Record
MGASA-2014-0059- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10423-1 No score
tor-0.2.8.11-1.1 on GA media
These are all security issues fixed in the tor-0.2.8.11-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10423-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
torDebian:12 |
before 0.2.4.20-1 | 0.2.4.20-1 |
torDebian:13 |
before 0.2.4.20-1 | 0.2.4.20-1 |
torDebian:14 |
before 0.2.4.20-1 | 0.2.4.20-1 |
torMageia:3 |
before 0.2.4.20-1.mga3 | 0.2.4.20-1.mga3 |
torMageia:4 |
before 0.2.4.20-1.mga4 | 0.2.4.20-1.mga4 |
toropenSUSE:Tumbleweed From an advisory covering 22 CVEs |
before 0.2.8.11-1.1 | 0.2.8.11-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2013-7295 is a medium vulnerability (CVSS 4.0) in Torproject Tor, published January 17, 2014. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.75%, the 77th percentile. Fixed in tor 0.2.4.20-1.
References
lists.opensuse.org/opensuse-updates/2014-01/msg00095.html
lists.torproject.org/pipermail/tor-talk/2013-December/031483.html
nvd.nist.gov/vuln/detail/CVE-2013-7295
github.com/advisories/GHSA-3x57-m985-pg67
security-tracker.debian.org/tracker/CVE-2013-7295
advisories.mageia.org/MGASA-2014-0059.html
Show 23 moreShow less
bugs.mageia.org/show_bug.cgi?id=12464
suse.com/security/cve/CVE-2011-0427