CVE-2012-4684

CVE-2012-4684 is a high-severity vulnerability in Bitcoin Bitcoin-qt with a CVSS 2.0 base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-399.

Key facts

Description

The alert functionality in bitcoind and Bitcoin-Qt before 0.7.0 supports different character representations of the same signature data, but relies on a hash of this signature, which allows remote attackers to cause a denial of service (resource consumption) via a valid modified signature for a circulating alert.

Frequently asked questions

What is CVE-2012-4684?
The alert functionality in bitcoind and Bitcoin-Qt before 0.7.0 supports different character representations of the same signature data, but relies on a hash of this signature, which allows remote attackers to cause a denial of service (resource consumption) via a valid modified signature for a circulating alert.
How severe is CVE-2012-4684?
CVE-2012-4684 has a CVSS 2.0 base score of 7.8, rated high severity.
Is CVE-2012-4684 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-4684?
CVE-2012-4684 primarily affects Bitcoin Bitcoin-qt. In total, 43 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-4684?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2012-4684 published?
CVE-2012-4684 was published on 2013-03-12 and last updated on 2026-06-16.

References

Affected products (43)

More vulnerabilities in Bitcoin Bitcoin-qt

All CVEs affecting Bitcoin Bitcoin-qt →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →