Skip to content

← Public intelligence

Go package

github.com/btcsuite/btcd

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.3GoPublished

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

    CVE-2024-38365 · GHSA-27vh-h6mc-q6g8

    Affected
    • Go github.com/btcsuite/btcd < 0.24.2-beta.rc1
    Fixed in
    0.24.2-beta.rc1· Vendor fix available
    Issue
    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 valid one). This consensus failure can be leveraged to cause a chain split (accepting an invalid Bitcoin block) or be exploited to DoS the btcd nodes (rejecting a valid Bitcoin block). An attacker can create a standard transaction where FindAndDelete doesn't return a match but removeOpCodeByData does making btcd get a different sighash, leading to a chain split. Importantly, this vulnerability can be exploited remotely by any Bitcoin user and does not require any hash power. This is because the difference in behavior can be triggered by a "standard" Bitcoin transaction, that is a transaction which gets relayed through the P2P network before it gets included in a Bitcoin block.…

    Recommended action: Upgrade to 0.24.2-beta.rc1 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedGoPublished

    btcd susceptible to consensus failures

    CVE-2024-34478 · GHSA-3jgf-r68h-xfqm

    Affected
    • Go github.com/btcsuite/btcd < 0.24.0
    Fixed in
    0.24.0· Vendor fix available
    Issue
    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 funds.

    Recommended action: Upgrade to 0.24.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.8GoPublished

    btcd mishandles witness size checking

    CVE-2022-44797 · GHSA-2chg-86hq-7w38

    Affected
    • Go github.com/btcsuite/btcd < 0.23.2
    Fixed in
    0.23.2· Vendor fix available
    Issue
    btcd before 0.23.2, as used in Lightning Labs lnd before 0.15.2-beta and other Bitcoin-related products, mishandles witness size checking. Specific Go Packages Affected github.com/btcsuite/btcd/wire

    Recommended action: Upgrade to 0.23.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →