dbcve.org
Bitcoin CoreApplication · Bitcoin

CVE-2024-52915

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 0.20.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message.

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 confidence

Bitcoin Core before version 0.20.0 contains a denial-of-service vulnerability where a remote attacker can send a crafted INV (inventory) message causing excessive memory consumption. The vulnerability stems from insufficient validation or limits on inventory messages, allowing an attacker to exhaust node memory.

MitigationUpgrade Bitcoin Core to version 0.20.0 or later. If immediate upgrade is not feasible, consider network-level restrictions limiting peer connections to trusted nodes.

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
Bitcoin CoreApplication
Affected:< 0.20.0

CVSS 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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Bitcoin Core version
    Run `bitcoin-cli version` or `bitcoind --version` to retrieve the exact version number of the Bitcoin Core software currently installed
    Affected if The reported version is lower than 0.20.0 (e.g., 0.19.x, 0.18.x, etc.)
  2. Confirm Bitcoin Core daemon is running
    Check if the bitcoind process is active using system commands such as `ps aux | grep bitcoind` or `systemctl status bitcoind`
    Affected if The daemon is running and the version from step 1 is below 0.20.0
  3. Verify network exposure
    Inspect the bitcoin.conf configuration file (typically located in ~/.bitcoin/ or /etc/bitcoin/) for `bind` or `listen` settings that allow external connections
    Affected if The node is configured to accept external (non-localhost) P2P connections and the version is below 0.20.0
  4. Review peer connection count
    Run `bitcoin-cli getpeerinfo` to list connected peers and observe the number of inbound connections
    Affected if The node has multiple inbound peer connections and the version is below 0.20.0, increasing the attack surface

You are affected if Bitcoin Core version is below 0.20.0, the daemon is running, and the node accepts external P2P connections, making it susceptible to memory exhaustion from crafted INV messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.20.0 or later
Fixed in 0.20.0
Interim mitigation

Upgrade Bitcoin Core to version 0.20.0 or later. If immediate upgrade is not feasible, consider network-level restrictions limiting peer connections to trusted nodes.

Recommended fix High confidence

Bitcoin Core 0.20.0 or later

  1. 1. Backup your Bitcoin Core data directory and wallet (if using a wallet) before upgrading
  2. 2. Download Bitcoin Core 0.20.0 or later from the official source at bitcoincore.org
  3. 3. Verify the downloaded binary using SHA256 checksums and/or GPG signatures as documented on the Bitcoin Core website
  4. 4. Safely stop the running Bitcoin Core instance (using 'bitcoin-cli stop' or the GUI stop option)
  5. 5. Install or extract the new Bitcoin Core version to replace the existing installation
  6. 6. Start the Bitcoin Core daemon or GUI application
  7. 7. Verify the running version matches the expected fixed version using 'bitcoin-cli getnetworkinfo' or the GUI debug console
Caveat Review Bitcoin Core release notes for any configuration or backward-incompatible changes between your current version and 0.20.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bitcoin Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52915 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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