# CVE-2024-34478: btcd susceptible to consensus failures

> Attackers can cause consensus failures and chain splits in btcd nodes by exploiting incorrect integer handling in transaction version checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2024
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3jgf-r68h-xfqm, GO-2024-2818

## What is CVE-2024-34478?

CVE-2024-34478 is a high-severity vulnerability in n/a, published on 5 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2024-34478?

3 open source packages ship an affected version, including github.com/btcsuite/btcd. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/btcsuite/btcd` | Go | All versions | 0.24.0 |
| `github.com/btcsuite/btcd` | Go | All versions | 0.24.0 |
| `github.com/btcsuite/btcd` | Go | All versions | 0.24.0 |

Products: Btcd Project Btcd.

## How do I fix CVE-2024-34478?

Upgrade github.com/btcsuite/btcd to 0.24.0 or later.

## Is CVE-2024-34478 being exploited?

There is no known exploitation of CVE-2024-34478 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-44797](https://insights.sbomify.com/CVE-2022-44797/): btcd mishandles witness size checking (critical 9.8)
- [CVE-2022-39389](https://insights.sbomify.com/CVE-2022-39389/): Witness Block Parsing DoS Vulnerability in lnd (high 8.2)
- [CVE-2024-38365](https://insights.sbomify.com/CVE-2024-38365/): btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34478 and fix it if it is affected.

What it is: CVE-2024-34478 is a high-severity vulnerability in n/a, published on 5 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34478 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/btcsuite/btcd (Go): affected all versions; fixed in 0.24.0
- github.com/btcsuite/btcd (Go): affected all versions; fixed in 0.24.0
- github.com/btcsuite/btcd (Go): affected all versions; fixed in 0.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-34478/ (Markdown: https://insights.sbomify.com/CVE-2024-34478/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34478
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34478
- OSV: https://osv.dev/vulnerability/CVE-2024-34478

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-34478/
Summaries are generated and may contain mistakes; the official description above is the record.