CVE-2020-8516
published 2020-02-02CVE-2020-8516: 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…
PriorityP427medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
2.50%
82.9th percentile
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
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | tor | — | — |
| torproject | tor | <= 0.4.1.8 | — |
| torproject | tor | 0.4.2.0 – 0.4.2.6 | — |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv5.3MEDIUM
vendor_debian5.3LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-gvvc-pv9r-rg5q: The daemon in Tor through 0
ghsa_unreviewed·2022-05-24
CVE-2020-8516 [MEDIUM] CWE-200 GHSA-gvvc-pv9r-rg5q: The daemon in Tor through 0
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.
OSV
CVE-2020-8516: ** DISPUTED ** The daemon in Tor through 0
osv·2020-02-02·CVSS 5.3
CVE-2020-8516 [MEDIUM] CVE-2020-8516: ** DISPUTED ** The daemon in Tor through 0
** DISPUTED ** 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.
OSV
CVE-2020-8516: The daemon in Tor through 0
osv·2020-02-02·CVSS 5.3
CVE-2020-8516 [MEDIUM] CVE-2020-8516: The daemon in Tor through 0
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
Debian
CVE-2020-8516: tor - The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify th...
vendor_debian·2020·CVSS 5.3
CVE-2020-8516 [MEDIUM] CVE-2020-8516: tor - The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify th...
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
Scope: local
bookworm: open
bullseye: open
forky: open
sid: open
trixie: open
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.htmlhttps://lists.torproject.org/pipermail/tor-dev/2020-February/014147.htmlhttps://security-tracker.debian.org/tracker/CVE-2020-8516https://trac.torproject.org/projects/tor/ticket/33129https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.htmlhttps://lists.torproject.org/pipermail/tor-dev/2020-February/014146.htmlhttps://lists.torproject.org/pipermail/tor-dev/2020-February/014147.htmlhttps://security-tracker.debian.org/tracker/CVE-2020-8516https://trac.torproject.org/projects/tor/ticket/33129https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html
2020-02-02
Published