CVE-2017-8822 json
In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and 0.3.1 before 0.3.1.9, relays…
published 2017-12-03 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17765
- cvss
- 3.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and 0.3.1 before 0.3.1.9, relays (that have incompletely downloaded descriptors) can pick themselves in a circuit path, leading to a degradation of anonymity, aka TROVE-2017-012.
Patch / fix
- tor_project tor 0.2.5.16, 0.2.8.17, 0.2.9.14, 0.3.0.13, 0.3.1.9
- tor Debian 14, Debian 13, Debian 12 0.3.1.9-1
debian advisories DEBIAN-CVE-2017-8822
- tor Ubuntu 14.04 LTS 0.2.4.27-1ubuntu0.1
- tor Ubuntu 16.04 LTS 0.2.9.14-1ubuntu1~16.04.2
ubuntu advisories UBUNTU-CVE-2017-8822
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- tor openSUSE Tumbleweed 0.4.6.7-2.2
- tor Package Hub 12 0.3.1.9-8.1
opensuse advisories openSUSE-SU-2024:11469-1openSUSE-SU-2017:3201-1openSUSE-SU-2017:3203-1
- tor Arch Linux 0.3.1.9-1
arch linux advisories AVG-539
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-8822 updated
tor: Multiple vulnerabilities
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 3.7 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- n/a Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and 0.3.1 before 0.3.1.9
Classification
- Weakness
-
- CWE-417 Communication Channel Errors
References
-
debian.org
/security/2017/dsa-4054
vendor-advisory, third-party-advisory
-
bugs.torproject.org
/21534
issue-tracking, vendor-advisory
-
blog.torproject.org
/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516
vendor-advisory
-
bugs.torproject.org
/24333
vendor-advisory
Sources
- CVE List CVE-2017-8822
- NVD CVE-2017-8822
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.