CVE-2024-38365 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality

btcd is an alternative full node bitcoin implementation written in Go golang. The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can...

CVE-2024-38365

CVE-2024-38365 affects btcd (versions 0.10 to 0.24). The issue is a mismatch in Bitcoin Core’s FindAndDelete() versus btcd’s removeOpcodeByData() that can cause btcd to validate blocks differently, risking a chain split (accepting an invalid block) or DoS (rejecting a valid block). The root cause...

CVE-2024-38365 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality

btcd is an alternative full node bitcoin implementation written in Go golang. The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can...

CVE-2024-38365 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality

btcd is an alternative full node bitcoin implementation written in Go golang. The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can...

CVE-2024-38365: Always-Incorrect Control Flow Implementation

btcd is an alternative full node bitcoin implementation written in Go golang. The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can...

btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality

Impact The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can lead to btcd clients accepting an invalid Bitcoin block or rejecting a...

GHSA-27VH-H6MC-Q6G8 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality

Impact The btcd Bitcoin client versions 0.10 to 0.24 did not correctly re-implement Bitcoin Core's "FindAndDelete" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can lead to btcd clients accepting an invalid Bitcoin block or rejecting a...

PT-2024-27962 · Btcd +1 · Btcd +1

Name of the Vulnerable Software and Affected Versions: btcd versions 0.10 through 0.24 Description: The btcd Bitcoin client did not correctly re-implement Bitcoin Core's 'FindAndDelete' functionality, leading to discrepancies in Bitcoin block validation. This can result in a chain split or Denial...

GO-2024-3112 CometBFT's state syncing validator from malicious node may lead to a chain split github.com/cometbft/cometbft

CometBFT's state syncing validator from malicious node may lead to a chain split github.com/cometbft/cometbft...

CometBFT's state syncing validator from malicious node may lead to a chain split

Name: ASA-2024-009: State syncing validator from malicious node may lead to a chain split Component: CometBFT Criticality: Medium ACMv1.2: I:Moderate; L: Possible Affected versions: = 0.34.0, =0.37.0, = 0.38.0, = 0.38.11 Summary The state sync protocol retrieves a snapshot of the application and...

Race Condition

btcd is vulnerable to a Race Condition. The vulnerability is due to the incorrect implementation of consensus rules as outlined in BIP 68 and BIP 112, specifically by treating the transaction version as a signed integer instead of unsigned. This misinterpretation can lead to a chain split and...

GHSA-3JGF-R68H-XFQM btcd susceptible to consensus failures

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

CVE-2024-34478

The btcd Bitcoin implementation (prior to version 0.24.0 ) contains a consensus failure vulnerability due to an incorrect implementation of BIP 68 and BIP 112 rules. The software incorrectly treats the transaction version as a signed integer instead of an unsigned integer. This discrepancy in con...

CVE-2024-34478: Interpretation Conflict

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

PT-2024-25929 · Btcd · Btcd

Name of the Vulnerable Software and Affected Versions: btcd versions prior to 0.24.0 Description: The issue arises from an incorrect implementation of the consensus rules outlined in BIP 68 and BIP 112, making btcd susceptible to consensus failures. Specifically, it uses the transaction version a...

Chain Split

github.com/ethereum/go-ethereum is vulnerable to Memory-Corruption. The vulnerability is due to mishandled memory copies during certain operations, like CALL-variants, leading to data corruption resulting in a consensus error and possible chain split...

Chain split caused by memory corruption in EVM

Lines of code Vulnerability details Chain split caused by memory corruption in EVM We recently found that the op-geth@3fa9e81 repository has a memory corruption vulnerability in EVM, which can cause a consensus error. Specifically, vulnerable nodes obtain a different stateRoot when processing a...