The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before attempting to connect to it, which might make it easier for remote attackers to discover circuit information. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerability
References
Link | Resource |
---|---|
https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html | Exploit Mitigation Technical Description Third Party Advisory |
https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html | Mailing List Vendor Advisory |
https://security-tracker.debian.org/tracker/CVE-2020-8516 | Third Party Advisory |
https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.html | Mailing List Vendor Advisory |
https://trac.torproject.org/projects/tor/ticket/33129 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
07 Nov 2023, 03:26
Type | Values Removed | Values Added |
---|---|---|
Summary | The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before attempting to connect to it, which might make it easier for remote attackers to discover circuit information. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerability |
Information
Published : 2020-02-02 13:15
Updated : 2024-08-04 10:15
NVD link : CVE-2020-8516
Mitre link : CVE-2020-8516
JSON object : View
Products Affected
torproject
- tor
CWE