Node stall via quadratic orphan processing
Published Nov 18, 2024 · Updated Nov 18, 2024
Denial of service in Bitcoin Core before 0.18.0 allows remote attackers to stall a node for hours via crafted unconfirmed transactions. After accepting a parent transaction into the mempool, orphan resolution scans up to 100 cached orphans for each new output and repeatedly validates deliberately invalid, expensive orphans. No authentication or user interaction is required; the affected node remains running but cannot process new network messages during the stall.
Summary
What happened
Denial of service in Bitcoin Core before 0.18.0 allows remote attackers to stall a node for hours via crafted unconfirmed transactions. After accepting a parent transaction into the mempool, orphan resolution scans up to 100 cached orphans for each new output and repeatedly validates deliberately invalid, expensive orphans. No authentication or user interaction is required; the affected node remains running but cannot process new network messages during the stall.
The record
- CVE
- CVE-2024-52914
- Published
- Nov 18, 2024
- Updated
- Nov 18, 2024
- Vendor
- Bitcoin
- Product
- Bitcoin Core
- Classifications
- CWE-770, T1499.004
- 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.18.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