Chain split via fuzzy signature removal
Published Oct 11, 2024 · Updated Oct 11, 2024
Consensus failure in btcsuite btcd before 0.24.2 allows remote attackers to split vulnerable nodes from the Bitcoin chain via a standard transaction. removeOpcodeByData removes every data push containing the signature bytes, while Bitcoin Core's FindAndDelete removes only exact matches, producing a different signature hash. Any Bitcoin user can relay the crafted standard transaction without hash power, causing an invalid-block chain split or rejection of a valid block that interrupts the node.
Summary
What happened
Consensus failure in btcsuite btcd before 0.24.2 allows remote attackers to split vulnerable nodes from the Bitcoin chain via a standard transaction. removeOpcodeByData removes every data push containing the signature bytes, while Bitcoin Core's FindAndDelete removes only exact matches, producing a different signature hash. Any Bitcoin user can relay the crafted standard transaction without hash power, causing an invalid-block chain split or rejection of a valid block that interrupts the node.
The record
- CVE
- CVE-2024-38365
- Published
- Oct 11, 2024
- Updated
- Oct 11, 2024
- Vendor
- btcsuite
- Product
- btcd
- Classifications
- CWE-670, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2024CVE publishedPublication date reported by the CVE source.
- Oct 11, 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.10.0, < 0.24.2
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