CVE-2013-2273 bitcoin
bitcoin: no CVSS score yet. EPSS 1.9% estimated probability of exploitation activity in the next 30 days.
bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x before 0.7.3rc1 make it easier for remote attackers to obtain potentially sensitive information about returned change by leveraging certain predictability in the outputs of a Bitcoin transaction.
- EPSS
- 1.9% (unchanged from 1.9% a week ago; 1.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 80th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2013-2273 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-2273?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-2273?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-2013-2273 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.
| Product | Affected |
|---|---|
| bitcoin:bitcoin-qt | through 0.4.8 |
| bitcoin:bitcoin-qt | 0.4:rc4 |
| bitcoin:bitcoin-qt | 0.5.0:rc1 |
| bitcoin:bitcoin-qt | 0.5.0.4 |
| bitcoin:bitcoin-qt | 0.5.1:rc1 |
| bitcoin:bitcoin-qt | 0.5.3.0 |
| bitcoin:bitcoin-qt | 0.5.7 |
| bitcoin:bitcoin-qt | 0.6.0.10:rc4 |
| bitcoin:bitcoin-qt | 0.6.3 |
| bitcoin:bitcoin-qt | 0.7.0:rc1 |
| bitcoin:bitcoin-qt | 0.7.1 |
| bitcoin:bitcoin-qt | 0.7.2 |
| bitcoin:bitcoin_core | 0.3.4 |
| bitcoin:bitcoin_core | 0.3.5 |
| bitcoin:bitcoin_core | 0.3.8 |
| bitcoin:bitcoin_core | 0.3.10 |
| bitcoin:bitcoin_core | 0.3.11 |
| bitcoin:bitcoin_core | 0.3.12 |
| bitcoin:bitcoin_core | 0.4.0 |
| bitcoin:bitcoin_core | 0.4.1 |
| bitcoin:bitcoin_core | 0.4.1:rc6 |
| bitcoin:bitcoin_core | 0.4.2 |
| bitcoin:bitcoin_core | 0.4.3 |
| bitcoin:bitcoin_core | 0.4.4 |
| bitcoin:bitcoin_core | 0.4.4:rc2 |
| bitcoin:bitcoin_core | 0.4.5 |
| bitcoin:bitcoin_core | 0.4.6 |
| bitcoin:bitcoin_core | 0.4.7:rc2 |
| bitcoin:bitcoin_core | 0.5.0:rc |
| bitcoin:bitcoin_core | 0.5.3 |
| bitcoin:bitcoin_core | 0.5.3.1 |
| bitcoin:bitcoin_core | 0.5.4 |
| bitcoin:bitcoin_core | 0.5.5 |
| bitcoin:bitcoin_core | 0.5.6:rc2 |
| bitcoin:bitcoin_core | 0.6.0.1 |
| bitcoin:bitcoin_core | 0.6.0.2 |
| bitcoin:bitcoin_core | 0.6.0.3 |
| bitcoin:bitcoin_core | 0.6.0.4 |
| bitcoin:bitcoin_core | 0.6.0.5 |
| bitcoin:bitcoin_core | 0.6.0.6 |
| bitcoin:bitcoin_core | 0.6.0.7 |
| bitcoin:bitcoin_core | 0.6.0.8 |
| bitcoin:bitcoin_core | 0.6.1 |
| bitcoin:bitcoin_core | 0.6.2 |
| bitcoin:bitcoind | through 0.4.4 |
| bitcoin:bitcoind | 0.5.7 |
| bitcoin:bitcoind | 0.6.0.0 |
| bitcoin:bitcoind | 0.6.0.10:rc4 |
| bitcoin:bitcoind | 0.6.3 |
| bitcoin:bitcoind | 0.6.4:rc4 |
| bitcoin:bitcoind | 0.7.0:rc1 |
| bitcoin:bitcoind | 0.7.1 |
| bitcoin:bitcoind | 0.7.2 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).