CVE-2024-52913
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 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.
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 0.21.0, transaction re-requests are mishandled in a way that allows an attacker to prevent a node from seeing a specific unconfirmed transaction. This is a denial-of-service style vulnerability affecting transaction relay.
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< 0.21.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.
-
Identify Bitcoin Core versionRun 'bitcoin-cli getnetworkinfo' and look for the 'version' field, or run 'bitcoind --version'Affected if The reported version is less than 210000 (which corresponds to version 0.21.0)
-
Verify transaction relay is enabledRun 'bitcoin-cli getnetworkinfo' and check if 'relay' is true in the output, or check config file for 'relay=1'Affected if Transaction relay is enabled and the version is below 0.21.0
-
Confirm node accepts network connectionsRun 'bitcoin-cli getnetworkinfo' and verify 'localaddresses' is non-empty or check that the node has active peers via 'getpeerinfo'Affected if The node accepts incoming network connections and version is below 0.21.0
A node is affected if it runs Bitcoin Core below version 0.21.0 with transaction relay enabled and network exposure to peers.
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 · scoped0.21.0
Upgrade Bitcoin Core to version 0.21.0 or later to address the transaction re-request mishandling.
Bitcoin Core 0.21.0 or later (recommended: latest stable release such as 26.x)
- 1. Backup your wallet.dat file and any important Bitcoin Core data directory
- 2. Ensure you have sufficient disk space for the upgraded node (additional ~50GB recommended for blockchain data)
- 3. Download the latest stable Bitcoin Core release from the official repository at github.com/bitcoin/bitcoin/releases
- 4. Stop the currently running Bitcoin Core node gracefully (do not force-kill)
- 5. Install or extract the new Bitcoin Core binaries
- 6. Start the new Bitcoin Core version and allow it to verify the blockchain from scratch or continue from where it left off
- 7. Monitor logs for any errors during startup and initial sync
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52913 — 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-52913 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