CPU exhaustion via oversized unparseable directory data
Published Mar 19, 2021 · Updated Aug 3, 2024
Denial of service in Tor before 0.4.5.7 allows remote attackers to exhaust CPU resources by sending crafted directory data. Several directory-parsing paths pass excessively long strings to dump_desc(), causing intensive processing while preparing unparseable information for disk output. Any participant able to send directory data can force sustained CPU consumption; authorities are easiest to target, while malicious caches can affect relays or clients.
Summary
What happened
Denial of service in Tor before 0.4.5.7 allows remote attackers to exhaust CPU resources by sending crafted directory data. Several directory-parsing paths pass excessively long strings to dump_desc(), causing intensive processing while preparing unparseable information for disk output. Any participant able to send directory data can force sustained CPU consumption; authorities are easiest to target, while malicious caches can affect relays or clients.
The record
- CVE
- CVE-2021-28089
- Published
- Mar 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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