Description
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
Metrics
CVSS 3.1 5.3/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NAffected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
References
- https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.htmlMailing List, Vendor Advisory
- https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.htmlMailing List, Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2020-8516Third Party Advisory
- https://trac.torproject.org/projects/tor/ticket/33129Issue Tracking, Vendor Advisory
- https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.htmlExploit, Mitigation, Technical Description, Third Party Advisory
- https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.htmlMailing List, Vendor Advisory
- https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.htmlMailing List, Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2020-8516Third Party Advisory
- https://trac.torproject.org/projects/tor/ticket/33129Issue Tracking, Vendor Advisory
- https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.htmlExploit, Mitigation, Technical Description, Third Party Advisory
Timeline
- Published
- Feb 2, 2020
- Last modified
- Jun 17, 2026
- NVD status
- Modified