Relay CPU exhaustion via circuit ID hash collisions
Published Jun 29, 2021 · Updated Aug 4, 2024
A denial-of-service flaw in Tor before 0.4.6.5 allows remote attackers to exhaust relay CPU via attacker-chosen circuit IDs. The circuitmux lookup uses a naive, unkeyed hash function, allowing chosen identifiers to collide and degrade hash-table operations. Any network peer able to create chosen circuit IDs against a relay can consume CPU and interrupt relay service without authentication.
Summary
What happened
A denial-of-service flaw in Tor before 0.4.6.5 allows remote attackers to exhaust relay CPU via attacker-chosen circuit IDs. The circuitmux lookup uses a naive, unkeyed hash function, allowing chosen identifiers to collide and degrade hash-table operations. Any network peer able to create chosen circuit IDs against a relay can consume CPU and interrupt relay service without authentication.
The record
- CVE
- CVE-2021-34549
- Published
- Jun 29, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2021CVE 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