| Name | CVE-2020-8516 |
| 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 |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| tor (PTS) | buster | 0.3.5.16-1 | vulnerable |
| buster (security) | 0.3.5.16-1+deb10u1 | vulnerable |
| bullseye (security), bullseye | 0.4.5.16-1 | vulnerable |
| bookworm, bookworm (security) | 0.4.7.16-1 | vulnerable |
| trixie | 0.4.8.10-1 | vulnerable |
| sid | 0.4.8.11-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| tor | source | (unstable) | (unfixed) | unimportant | | |
Notes
Not considered a bug / explicit design choice by upstream
https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html
https://trac.torproject.org/projects/tor/ticket/33129
http://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html