CVE-2024-52922: Medium severity bitcoin vulnerability
Published Nov 18, 2024
·Updated
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.
Affected Software
2 affected components
Bitcoin Core<25.1
Bitcoin Bitcoin Core<25.1
Event History
Nov 18, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·04:15 AM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-52922?
CVE-2024-52922 has been assessed as a medium severity vulnerability due to its potential impact on block synchronization.
2
How do I fix CVE-2024-52922?
To mitigate CVE-2024-52922, upgrade your Bitcoin Core software to version 25.1 or later.
3
What versions of Bitcoin Core are affected by CVE-2024-52922?
CVE-2024-52922 affects all versions of Bitcoin Core prior to 25.1.
4
What is the impact of CVE-2024-52922 on Bitcoin nodes?
CVE-2024-52922 can cause a Bitcoin node to experience delays in downloading new blocks due to peer stalls.
5
Is CVE-2024-52922 a protocol compliance issue?
Yes, CVE-2024-52922 arises from non-compliance with the peer-to-peer protocol specifications.