cve.bz

CVE-2012-1910 bitcoin

no score yetExploit referenceEPSS 4.5%Fix available

bitcoin: no CVSS score yet. EPSS 4.5% estimated probability of exploitation activity in the next 30 days.

Bitcoin-Qt 0.5.0.x before 0.5.0.5; 0.5.1.x, 0.5.2.x, and 0.5.3.x before 0.5.3.1; and 0.6.x before 0.6.0rc4 on Windows does not use MinGW multithread-safe exception handling, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via crafted Bitcoin protocol messages.
EPSS
4.5% (unchanged from 4.5% a week ago; 4.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2012-1910 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2012-1910?via=ask-ai-copy and https://cve.bz/cve/CVE-2012-1910?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2012-1910 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
bitcoin:bitcoin-qt0.5.0:rc1
bitcoin:bitcoin-qt0.5.0.4
bitcoin:bitcoin-qt0.5.1:rc1
bitcoin:bitcoin-qt0.5.3.0
bitcoin:bitcoin_core0.5.0
bitcoin:bitcoin_core0.5.1
bitcoin:bitcoin_core0.5.2
bitcoin:bitcoin_core0.6.0
bitcoin:bitcoin_core0.6.0:rc1
bitcoin:bitcoin_core0.6.0:rc3

References

Check your stackJSON