CVE-2024-52913
published 2024-11-18CVE-2024-52913: In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.
PriorityP425medium5.3CVSS 3.1
AVNACLPRNUINSUCNINAL
EPSS
0.37%
28.4th percentile
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| bitcoin | bitcoin_core | < 0.21.0 | 0.21.0 |
| bitcoin | bitcoin_core | <= 27.2 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-82x2-v3jv-gmrq: Bitcoin Core through 27
ghsa_unreviewed·2024-12-09·CVSS 5.3
CVE-2024-55563 [MEDIUM] GHSA-82x2-v3jv-gmrq: Bitcoin Core through 27
Bitcoin Core through 27.2 allows transaction-relay jamming via an off-chain protocol attack, a related issue to CVE-2024-52913. For example, the outcome of an HTLC (Hashed Timelock Contract) can be changed because a flood of transaction traffic prevents propagation of certain Lightning channel transactions.
GHSA
GHSA-h7hm-94xj-mhpm: In Bitcoin Core before 0
ghsa_unreviewed·2024-11-18
CVE-2024-52913 [MEDIUM] CWE-770 GHSA-h7hm-94xj-mhpm: In Bitcoin Core before 0
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-11-18
Published