CVE-2020-10593 json
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), a…
published 6y ago modified 4mo ago also EUVD-2020-3043
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), aka TROVE-2020-004. This occurs in circpad_setup_machine_on_circ because a circuit-padding machine can be negotiated twice on the same circuit.
Patch / fix
- torproject tor 0.3.5.10, 0.4.1.9
- tor Debian 14, Debian 13, Debian 12 0.4.2.7-1
debian advisories DEBIAN-CVE-2020-10593
- tor openSUSE Tumbleweed 0.4.6.7-2.2
- tor Package Hub 15 SP2, Package Hub 15 SP1, Package Hub 12 +2 more 0.4.4.6-bp152.2.3.1
- tor Package Hub 15 SP1 0.3.5.10-bp151.3.3.1
- tor openSUSE Leap 15.1 0.3.5.10-lp151.2.3.1
opensuse advisories openSUSE-SU-2024:11469-1openSUSE-SU-2020:1970-1openSUSE-SU-2020:0428-1openSUSE-SU-2020:0406-1
- tor Alpine 3.10 0.3.5.10-r0
- tor Alpine 3.11 0.4.4.9-r0
- tor Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 0.4.2.7-r0
alpine advisories ALPINE-CVE-2020-10593
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2020-10593 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-10593 updated cvss 7.5
tor: there's a memory leak allowing remote attackers to cause a DoS
-
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
2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
security.gentoo.org
/glsa/202003-50
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-03/msg00045.html
vendor-advisory, mailing-list, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-03/msg00052.html
vendor-advisory, mailing-list, third-party-advisory
-
trac.torproject.org
/projects/tor/ticket/33619
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2020-10593
- NVD CVE-2020-10593
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.