How severe is CVE-2013-7295?

CVE-2013-7295 has a CVSS 2.0 base score of 4.0, rated medium severity.

Is CVE-2013-7295 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2013-7295?

CVE-2013-7295 primarily affects Torproject Tor. In total, 19 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2013-7295?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2013-7295 published?

CVE-2013-7295 was published on 2014-01-17 and last updated on 2026-06-17.

CVE-2013-7295

CVE-2013-7295 is a medium-severity vulnerability in Torproject Tor with a CVSS 2.0 base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Severity: Medium (CVSS 2.0 base score 4.0)
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-310
Affected product: Torproject Tor
Published: 2014-01-17
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2013-7295?: CVE-2013-7295 has a CVSS 2.0 base score of 4.0, rated medium severity.
Is CVE-2013-7295 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-7295?: CVE-2013-7295 primarily affects Torproject Tor. In total, 19 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-7295?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-7295 published?: CVE-2013-7295 was published on 2014-01-17 and last updated on 2026-06-17.

References

Affected products (19)

cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.1:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.2:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.3:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.4:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.5:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.6:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.7:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.8:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.9:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.10:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.11:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.12:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.13:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.14:alpha:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.15:rc:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.16:rc:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.17:rc:*:*:*:*:*:*
cpe:2.3:a:torproject:tor:0.2.4.18:rc:*:*:*:*:*:*

More vulnerabilities in Torproject Tor

CVE-2022-33903 — High (CVSS 7.5): Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation.
CVE-2021-38385 — High (CVSS 7.5): Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and…
CVE-2021-34550 — High (CVSS 7.5): An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006. The v3 onion service descriptor parsing allows…
CVE-2021-34549 — High (CVSS 7.5): An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain retrieval of…
CVE-2021-34548 — High (CVSS 7.5): An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-003. An attacker can forge RELAY_END or RELAY_RESOLVED to…
CVE-2021-28089 — High (CVSS 7.5): Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resources on a target, aka…

All CVEs affecting Torproject Tor →

Other CWE-310 (Cryptographic Issues) vulnerabilities

CVE-2014-7878 — Critical (CVSS 10.0): The Application Lifecycle Service (ALS) in HP Helion Cloud Development Platform 1.0, when a virtual machine is derived…
CVE-2013-3712 — Critical (CVSS 10.0): SUSE Studio Onsite 1.3.x before 1.3.6 and SUSE Studio Extension for System z 1.3 uses "static" secret tokens, which has…
CVE-2013-6952 — Critical (CVSS 10.0): The Belkin WeMo Home Automation firmware before 3949 has a hardcoded GPG key, which makes it easier for remote…
CVE-2013-6838 — Critical (CVSS 10.0): An unspecified Enghouse Interactive Professional Services "addon product" in Enghouse Interactive IVR Pro (VIP2000)…
CVE-2013-0137 — Critical (CVSS 10.0): The default configuration of the Digital Alert Systems DASDEC EAS device before 2.0-2 and the Monroe Electronics R189…
CVE-2011-5123 — Critical (CVSS 10.0): The Antivirus component in Comodo Internet Security before 5.3.175888.1227 does not check whether X.509 certificates in…

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →