Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2016-10724

Bitcoin Core before v0.13.0 allows denial of service (memory exhaustion) triggered by the remote network alert system (deprecated since Q1 2016) if an attacker can sign a message with a certain private key that had been known by unintended actors, because of an infinitely sized map. This affects other uses of the codebase, such as Bitcoin Knots before v0.13.0.knots20160814 and many altcoins.

Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 3 products from bitcoin, from bitcoin, from bitcoin organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2018, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.

Published

2018-07-05T22:29:00.233

Last Modified

2024-11-21T02:44:35.993

Status

Modified

Source

[email protected]

Severity

CVSSv3.0: 7.5 (HIGH)

CVSSv2 Vector

AV:N/AC:L/Au:N/C:N/I:N/A:C

Access Vector: NETWORK
Access Complexity: LOW
Authentication: NONE
Confidentiality Impact: NONE
Integrity Impact: NONE
Availability Impact: COMPLETE

Exploitability Score

10.0

Impact Score

6.9

Weaknesses

Type: Primary
CWE-400

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	bitcoin	bitcoin_core	< 0.13.0	Yes
Application	bitcoin	bitcoin-qt	< 0.13.0	Yes
Application	bitcoin	bitcoind	< 0.13.0	Yes

References

https://bitcoin.org/en/posts/alert-key-and-vulnerabilities-disclosure ([email protected])
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures Vendor Advisory ([email protected])
https://github.com/JinBean/CVE-Extension ([email protected])
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016189.html Third Party Advisory ([email protected])
https://bitcoin.org/en/posts/alert-key-and-vulnerabilities-disclosure (af854a3a-2127-422b-91ae-364da2661108)
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures Vendor Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://github.com/JinBean/CVE-Extension (af854a3a-2127-422b-91ae-364da2661108)
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016189.html Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For bitcoin's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.