Unscored severity · published Aug 2, 2013
CVE-2013-3220
bitcoind and Bitcoin-Qt before 0.4.9rc2, 0.5.x before 0.5.8rc2, 0.6.x before 0.6.5rc2, and 0.7.x before 0.7.3rc2, and wxBitcoin, do not properly consider whether a block's size…
–
CVSS
2.3%
EPSS
No
On KEV
Description
bitcoind and Bitcoin-Qt before 0.4.9rc2, 0.5.x before 0.5.8rc2, 0.6.x before 0.6.5rc2, and 0.7.x before 0.7.3rc2, and wxBitcoin, do not properly consider whether a block's size could require an excessive number of database locks, which allows remote attackers to cause a denial of service (split) and enable certain double-spending capabilities via a large block that triggers incorrect Berkeley DB locking.
Exploitation
Is it being used?
Exploit prediction (EPSS)2.3% · higher than 83% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
BC
Bitcoin Core · Bitcoin
0.3.4; 0.3.5; 0.3.8; 0.3.10; 0.3.11; 0.3.12; +26 more · source: NVD
BI
Bitcoin-qt · Bitcoin
through 0.4.9; 0.4; 0.4.8; 0.5.0; 0.5.0.4; 0.5.1; +9 more · source: NVD
BI
Bitcoind · Bitcoin
through 0.4.9; 0.4.4; 0.5.7; 0.5.8; 0.6.0.0; 0.6.0.10; +7 more · source: NVD
QI
Qitcoin-qt · Bitcoin
0.6.4; 0.6.5 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2013-3220
CVE.org
https://www.cve.org/CVERecord?id=CVE-2013-3220
Vendor Advisory
https://en.bitcoin.it/wiki/BIP_0050
Vendor Advisory
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures
More from Bitcoin Core
9.8
CVE-2015-20111
miniupnp before 4c90b87, as used in Bitcoin Core before 0.12 and other products, lacks checks for snprintf return values, leading to a buffer overflow and significant data leak, a…
7.5
CVE-2025-46597
Bitcoin Core 0.13.0 through 29.x has an integer overflow
7.5
CVE-2025-54605
Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 2 of 2)
7.5
CVE-2025-54604
Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2)
7.5
CVE-2024-52912
Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an abs64 logic bug
