Service interruption via remote CPU exhaustion
Published Mar 23, 2020 · Updated Aug 4, 2024
Denial of service in Tor before 0.3.5.10, before 0.4.1.9, and before 0.4.2.7 allows remote attackers to interrupt service via CPU exhaustion. The Tor Project has not published the malformed protocol input or processing routine that drives the excessive computation. Any remote user can repeatedly target a relay or authority, while a directory cache can target connected clients or onion services, causing disruptions lasting seconds or minutes and potentially creating traffic-analysis patterns.
Summary
What happened
Denial of service in Tor before 0.3.5.10, before 0.4.1.9, and before 0.4.2.7 allows remote attackers to interrupt service via CPU exhaustion. The Tor Project has not published the malformed protocol input or processing routine that drives the excessive computation. Any remote user can repeatedly target a relay or authority, while a directory cache can target connected clients or onion services, causing disruptions lasting seconds or minutes and potentially creating traffic-analysis patterns.
The record
- CVE
- CVE-2020-10592
- Published
- Mar 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- 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