Remote node crash via amplified GETHEADERS buffering
Published Nov 18, 2024 · Updated Nov 18, 2024
Resource exhaustion in Bitcoin Core before 0.20.0 allows remote attackers to crash nodes through a crafted INV message. In ProcessMessages(), one INV containing 50,000 block entries queues 50,000 roughly 1 KB GETHEADERS responses when the peer refuses to read them. An unauthenticated P2P peer can consume about 50 MB per connection, and concurrent peers can exhaust memory and terminate the node.
Summary
What happened
Resource exhaustion in Bitcoin Core before 0.20.0 allows remote attackers to crash nodes through a crafted INV message. In ProcessMessages(), one INV containing 50,000 block entries queues 50,000 roughly 1 KB GETHEADERS responses when the peer refuses to read them. An unauthenticated P2P peer can consume about 50 MB per connection, and concurrent peers can exhaust memory and terminate the node.
The record
- CVE
- CVE-2024-52915
- Published
- Nov 18, 2024
- Updated
- Nov 18, 2024
- Vendor
- Bitcoin
- Product
- Bitcoin Core
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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