CVE-2013-7295: n/a vulnerability

CVE-2013-7295: Tor before 0.2.4.20, when OpenSSL 1.x is used in conjunction with a certain HardwareAccel setting on Intel...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 18:01 UTC (UTC+00:00)

Security readout for executives and security teams

This flaw affects older Tor deployments only under a specific hardware and OpenSSL acceleration combination. If present, Tor could have generated weak relay or hidden-service identity keys, potentially weakening cryptographic trust. The public bundle does not provide CVSS, active exploitation evidence, or detailed attack mechanics. Exposure appears limited to Tor versions before 0.2.4.20 on Intel Sandy Bridge or Ivy Bridge platforms using OpenSSL 1.x with the relevant HardwareAccel setting. The bundle does not identify CPEs, distributions beyond the cited openSUSE advisory, or exact configuration values. Prioritize review for any organization operating Tor relays or hidden services on legacy hardware. For most environments, urgency is bounded by narrow prerequisites and the age of the affected versions, but identity-key weakness can carry long-term trust implications. Mitigation focus: Upgrade Tor to 0.2.4.20 or a vendor-supported fixed release.; Review openSUSE or applicable vendor advisories for packaged fixes.; Identify systems using Tor with OpenSSL 1.x and hardware acceleration enabled..

Prepared: Jun 14, 2026, 14:50 UTC (UTC+00:00)

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-2013-7295 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: Jan 17, 2014, 19:00 UTC (UTC+00:00)

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

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
[tor-talk] 20131223 Tor 0.2.4.20 is releasedCVE reference · mailing-list, x_refsource_MLIST

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.