CVE-2024-52913Network attack vector

Transaction censorship via evictable re-request tracking

Published Nov 18, 2024 · Updated Nov 18, 2024

Transaction re-request handling in Bitcoin Core before 0.21.0 allows remote attackers to hide a specific unconfirmed transaction from a node. The SendMessages function records each request in the 50,000-entry g_already_asked_for limitedmap, whose oldest-entry eviction lets bogus announcements remove the target and restart its request queue. A malicious peer must announce the target first, withhold it, flood enough bogus announcements to evict its record, and repeatedly reannounce it, preventing that node from requesting the transaction from honest peers.

CVSS severity5.3
Medium
EPSS probability0.38%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Transaction re-request handling in Bitcoin Core before 0.21.0 allows remote attackers to hide a specific unconfirmed transaction from a node. The SendMessages function records each request in the 50,000-entry g_already_asked_for limitedmap, whose oldest-entry eviction lets bogus announcements remove the target and restart its request queue. A malicious peer must announce the target first, withhold it, flood enough bogus announcements to evict its record, and repeatedly reannounce it, preventing that node from requesting the transaction from honest peers.

The record

CVE
CVE-2024-52913
Published
Nov 18, 2024
Updated
Nov 18, 2024
Vendor
Bitcoin
Product
Bitcoin Core
Classifications
CWE-770, T1498
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 18, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 18, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.21.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Bitcoin · Bitcoin Coreversion=0 <0.21.0

Published CVSS scores

5.3CISA ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-770Allocation of Resources Without Limits or Throttling
T1498Network Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo