dbcve.org
Bitcoin CoreApplication · Bitcoin

CVE-2024-52922

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 25.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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
In Bitcoin Core before 25.1, an attacker can cause a node to not download the latest block, because there can be minutes of delay when an announcing peer stalls instead of complying with the peer-to-peer protocol specification.

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

In Bitcoin Core before 25.1, a malicious peer can exploit the block announcement mechanism by stalling instead of following the peer-to-peer protocol specification, causing the victim node to experience minutes of delay in downloading the latest block. This creates a window where the node is out of sync with the current blockchain state.

MitigationUpgrade Bitcoin Core to version 25.1 or later to patch the vulnerability. Consider monitoring peer behavior and implementing network-level controls to detect non-compliant peers.

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:< 25.1

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
Low
Integrity
Low
Availability
None

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

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 getnetworkinfo' or check the Bitcoin Core application details. Look for the 'version' field in the output.
    Affected if The version number is less than 250100 (25.1). Compare your version against the affected range of versions before 25.1.
  2. Verify P2P networking is enabled
    Run 'bitcoin-cli getnetworkinfo' and check the 'localaddresses' field, or run 'bitcoin-cli getpeerinfo' to list connected peers.
    Affected if The node has incoming or outgoing peer connections enabled. The vulnerability requires the node to be connected to peers over the P2P network.
  3. Confirm active peer connections exist
    Run 'bitcoin-cli getpeerinfo' and count the number of connected peers in the output.
    Affected if The node has one or more connected peers. A malicious peer can only exploit this vulnerability when connected to the target node.
  4. Check node sync status and block height
    Run 'bitcoin-cli getblockchaininfo' and examine the 'initialblockdownload' field and compare your 'blocks' height with network height.
    Affected if The node shows a significant lag in sync status or block height compared to the expected chain height, which could indicate the delay exploitation.

If the installed Bitcoin Core version is before 25.1 and the node maintains active P2P peer connections, the node is potentially affected by this block announcement stalling vulnerability.

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 25.1 or later
Fixed in 25.1
Interim mitigation

Upgrade Bitcoin Core to version 25.1 or later to patch the vulnerability. Consider monitoring peer behavior and implementing network-level controls to detect non-compliant peers.

Recommended fix Moderate confidence

Bitcoin Core 25.1

  1. 1. Backup your Bitcoin Core data directory and configuration files before making any changes
  2. 2. Download Bitcoin Core version 25.1 or later from the official repository at bitcoincore.org
  3. 3. Stop the running Bitcoin Core node gracefully (do not force-kill)
  4. 4. Replace the Bitcoin Core binaries with the new version
  5. 5. Start the Bitcoin Core node and verify it is running the updated version using `bitcoin-cli getnetworkinfo` or `bitcoin-cli getblockchaininfo`
  6. 6. Monitor the node for normal operation and ensure it syncs to the latest block

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

Fix this in Bitcoin Core Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52922 — 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-52922 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