Vulnerabilities · 2020 · Torproject
CVE-2020-8516
Torproject Tor vulnerability
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
Affected products
Tor. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Torproject Tor runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- lists.torproject.org/pipermail/tor-dev/2020-February/014146.html · Vendor Advisory
- lists.torproject.org/pipermail/tor-dev/2020-February/014147.html · Vendor Advisory
- trac.torproject.org/projects/tor/ticket/33129 · Vendor Advisory
- www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html · Exploit
- security-tracker.debian.org/tracker/CVE-2020-8516 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-8516
- cve.org/CVERecord?id=CVE-2020-8516
More vulnerabilities in Torproject products
CVE-2023-23589CVE-2022-33903CVE-2021-46702CVE-2021-39246CVE-2021-38385CVE-2021-34550CVE-2021-34549CVE-2021-34548All 40
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.