CVE-2024-52921
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Bitcoin Core before version 25.0, a vulnerability exists in the P2P network layer where a malicious peer can send a mutated (malformed) block to affect the download state of other connected peers. This can cause nodes to enter incorrect download states, potentially wasting resources or causing synchronization issues.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 25.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Bitcoin Core daemon is runningRun `bitcoin-cli getblockchaininfo` or `bitcoin-cli getnetworkinfo`. If these commands succeed, the node is running and accessible.Affected if The node is not running or not accessible via bitcoin-cli.
-
Retrieve the Bitcoin Core versionRun `bitcoin-cli getnetworkinfo` and look for the `version` field in the output, or run `bitcoind --version` to see the version number.Affected if Unable to retrieve version information.
-
Compare version against the affected rangeThe affected version range is anything less than 25.0. Compare your retrieved version number to 25.0 (version 250000 in the numeric format Bitcoin Core uses).Affected if Your version is below 250000 (i.e., 24.x.x or earlier).
-
Verify P2P network participationRun `bitcoin-cli getpeerinfo` to confirm the node has active peer connections. This vulnerability exploits the P2P block download mechanism, so the node must be connected to peers.Affected if The node has zero connected peers, though this only reduces exploitability rather than confirming safety.
You are affected if your Bitcoin Core version is below 25.0 (numeric version 250000) and the node is running with P2P connectivity.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped25.0
Upgrade Bitcoin Core to version 25.0 or later to obtain the fix for this vulnerability.
Bitcoin Core 25.0 or later
- Backup your Bitcoin Core data directory and any wallets before upgrading
- Download Bitcoin Core 25.0 or later from the official source at bitcoincore.org
- Verify the GPG signature of the downloaded binary using Bitcoin Core release signing keys (follow the official verification guide)
- Stop the running Bitcoin Core daemon safely (e.g., using 'bitcoin-cli stop' or sending SIGTERM)
- Install the new Bitcoin Core 25.0 binary, replacing the previous installation
- Restart the Bitcoin Core daemon
- Monitor the debug.log for any errors or issues following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52921 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data