Remote node crash via repeated FillBlock call
Published Oct 10, 2024 · Updated Oct 10, 2024
Denial of service in Bitcoin Core before 25.0 allows remote attackers to crash a node through a crafted blocktxn message. The blocktxn handler leaves the PartiallyDownloadedBlock and request state intact after a merkle-root mismatch, allowing a second FillBlock call to violate its single-use assertion. Any network peer can trigger the path without authentication by supplying transactions absent from the announced block, terminating the node process.
Summary
What happened
Denial of service in Bitcoin Core before 25.0 allows remote attackers to crash a node through a crafted blocktxn message. The blocktxn handler leaves the PartiallyDownloadedBlock and request state intact after a merkle-root mismatch, allowing a second FillBlock call to violate its single-use assertion. Any network peer can trigger the path without authentication by supplying transactions absent from the announced block, terminating the node process.
The record
- CVE
- CVE-2024-35202
- Published
- Oct 10, 2024
- Updated
- Oct 10, 2024
- Vendor
- Bitcoin
- Product
- Bitcoin Core
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2024CVE publishedPublication date reported by the CVE source.
- Oct 10, 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 <25.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