# CVE-2024-35202: Bitcoin Core before 25.0 allows remote attackers to cause a denial of service (blocktxn message-handling assertion and node exit) by includi


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Oct 2024
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-53v9-6jr7-7fxh

## What is CVE-2024-35202?

CVE-2024-35202 is a high-severity vulnerability in Bitcoin Bitcoin Core, published on 10 Oct 2024. 

### Official description

Bitcoin Core before 25.0 allows remote attackers to cause a denial of service (blocktxn message-handling assertion and node exit) by including transactions in a blocktxn message that are not committed to in a block's merkle root. FillBlock can be called twice for one PartiallyDownloadedBlock instance.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Bitcoin Bitcoin Core.

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

Upgrade to a fixed version.

## Is CVE-2024-35202 being exploited?

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

## Other vulnerabilities in Bitcoin Bitcoin Core

- [CVE-2025-46597](https://insights.sbomify.com/CVE-2025-46597/): Integer overflow in n/a (high 7.5)
- [CVE-2025-54604](https://insights.sbomify.com/CVE-2025-54604/): Denial of service in n/a (high 7.5)
- [CVE-2025-54605](https://insights.sbomify.com/CVE-2025-54605/): Denial of service in n/a (high 7.5)
- [CVE-2019-25220](https://insights.sbomify.com/CVE-2019-25220/): Denial of service in n/a (high 7.5)
- [CVE-2024-52912](https://insights.sbomify.com/CVE-2024-52912/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35202 is a high-severity vulnerability in Bitcoin Bitcoin Core, published on 10 Oct 2024. 
Exploitation: There is no known exploitation of CVE-2024-35202 in the wild and no public exploit code.

Affected product: Bitcoin Bitcoin Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-35202/ (Markdown: https://insights.sbomify.com/CVE-2024-35202/index.md)
```

## Sources

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

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