Chain split via signed transaction-version checks
Published May 5, 2024 · Updated Aug 7, 2024
Consensus-rule error in btcd before 0.24.0 allows remote attackers to split the chain via negative transaction versions. The BIP 68 sequence-lock test and BIP 112 CHECKSEQUENCEVERIFY path compare a signed int32 version directly instead of casting it to uint32. A negative-version transaction must enter a block; disagreement with other Bitcoin implementations can strand the node on a divergent chain and expose dependent users to invalid payments or lost funds.
Summary
What happened
Consensus-rule error in btcd before 0.24.0 allows remote attackers to split the chain via negative transaction versions. The BIP 68 sequence-lock test and BIP 112 CHECKSEQUENCEVERIFY path compare a signed int32 version directly instead of casting it to uint32. A negative-version transaction must enter a block; disagreement with other Bitcoin implementations can strand the node on a divergent chain and expose dependent users to invalid payments or lost funds.
The record
- CVE
- CVE-2024-34478
- Published
- May 5, 2024
- Updated
- Aug 7, 2024
- Vendor
- btcsuite
- Product
- btcd
- Classifications
- CWE-436, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 7, 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.24.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
- Negative-version testnet transactionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Public testnet chain-stall observationreported exploitation
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