CVE-2020-8516

low-risk
Published 2020-02-02

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

Do I need to act?

-
0.78% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10 Medium
NETWORK / LOW complexity

Affected Products (1)

Tor

Affected Vendors

Torproject

References (10)

Mailing List https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.html
Mailing List https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html
Third Party Advisory https://security-tracker.debian.org/tracker/CVE-2020-8516
Issue Tracking https://trac.torproject.org/projects/tor/ticket/33129
Exploit https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circ...
Mailing List https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.html
Mailing List https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html
Third Party Advisory https://security-tracker.debian.org/tracker/CVE-2020-8516
Issue Tracking https://trac.torproject.org/projects/tor/ticket/33129
Exploit https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circ...
29
/ 100
low-risk
Severity 21/34 · High
Exploitability 3/34 · Minimal
Exposure 5/34 · Minimal