Service interruption via duplicate padding-machine negotiation
Published Mar 23, 2020 · Updated Aug 4, 2024
Memory leak in 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 interrupt service. The circpad_setup_machine_on_circ function continued after nonfatal assertions detected existing padding-machine state, allowing duplicate registration and leaked allocations. An unauthenticated peer that renegotiates circuit padding on the same circuit can repeatedly consume process memory until the Tor instance becomes unavailable.
Summary
What happened
Memory leak in 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 interrupt service. The circpad_setup_machine_on_circ function continued after nonfatal assertions detected existing padding-machine state, allowing duplicate registration and leaked allocations. An unauthenticated peer that renegotiates circuit padding on the same circuit can repeatedly consume process memory until the Tor instance becomes unavailable.
The record
- CVE
- CVE-2020-10593
- Published
- Mar 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo