Block propagation disruption via cross-peer state clearing
Published Nov 18, 2024 · Updated Nov 18, 2024
Missing authorization in Bitcoin Core before 25.0 allows remote attackers to hinder block propagation by sending a mutated block. An unrequested mutated block clears compact-block reconstruction and download state belonging to peers that announced the same block, so a later blocktxn response cannot complete reconstruction. Any unauthenticated P2P peer can trigger the state change; the bounded consequence is delayed block relay rather than data disclosure or modification.
Summary
What happened
Missing authorization in Bitcoin Core before 25.0 allows remote attackers to hinder block propagation by sending a mutated block. An unrequested mutated block clears compact-block reconstruction and download state belonging to peers that announced the same block, so a later blocktxn response cannot complete reconstruction. Any unauthenticated P2P peer can trigger the state change; the bounded consequence is delayed block relay rather than data disclosure or modification.
The record
- CVE
- CVE-2024-52921
- Published
- Nov 18, 2024
- Updated
- Nov 18, 2024
- Vendor
- Bitcoin
- Product
- Bitcoin Core
- Classifications
- CWE-862, T1498
- 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 <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.
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