Bug 486706 - (CVE-2009-0654) CVE-2009-0654 tor: allows breaking its anonymity via single cell
CVE-2009-0654 tor: allows breaking its anonymity via single cell
Status: CLOSED UPSTREAM
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
http://www.blackhat.com/presentations...
public=20090216,reported=20090220,imp...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-21 05:43 EST by Jan Lieskovsky
Modified: 2011-01-20 16:46 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-20 16:46:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2009-02-21 05:43:34 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2009-0654 to
the following vulnerability:

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."

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0654
http://blog.torproject.org/blog/one-cell-enough
http://www.blackhat.com/html/bh-dc-09/bh-dc-09-archives.html#Fu
http://www.blackhat.com/presentations/bh-dc-09/Fu/BlackHat-DC-09-Fu-Break-Tors-Anonymity.pdf
Comment 1 Vincent Danen 2011-01-20 16:46:27 EST
We do not have any supported products with tor 0.2.0.x, so closing this.

Note You need to log in before you can comment on or make changes to this bug.