LiveActive security incident?Get immediate response
CVE Record

CVE-2009-0654: Tor 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router a...

Tor 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router and an exit router, to confirm that a sender and receiver are communicating via vectors involving (1) replaying, (2) modifying, (3) inserting, or (4) deleting a single cell, and then observing cell recognition errors at the exit router. NOTE: the vendor disputes the significance of this issue, noting that the product's design "accepted end-to-end correlation as an attack that is too expensive to solve."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue concerns older Tor versions where an attacker controlling both the entry and exit router could confirm that two parties were communicating. The harm is loss of anonymity, not system takeover. The vendor disputed the practical significance, noting that Tor already treats end-to-end correlation as an accepted design risk. Exposure is likely limited to environments using the named older Tor versions or relying on them for anonymity-sensitive workflows. The source bundle does not identify affected CPEs, supported platforms, or a vendor patch state. Treat this as a targeted anonymity risk, not a broad infrastructure compromise. Prioritize if the organization used the affected Tor versions for sensitive communications, investigations, whistleblower channels, or other workflows where confirming relationships creates business or safety impact. Mitigation focus: Inventory any use of Tor 0.2.0.28, 0.2.0.34, or earlier.; Review Tor Project guidance before deciding technical remediation.; Avoid relying on affected versions for high-sensitivity anonymity workflows..

Prepared

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-2009-0654 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
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
1Source links

CVSS and timeline data

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

Source materials

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.