CVE-2013-2273: Infoleak

Published Mar 12, 2013
·
Updated

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.

Affected Software

54 affected components
Bitcoin Bitcoin-Qt<=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
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<=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

Event History

Mar 12, 2013
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-2273?

CVE-2013-2273 has been classified as a medium severity vulnerability.

2

How do I fix CVE-2013-2273?

To fix CVE-2013-2273, upgrade to a version of Bitcoin-Qt or bitcoind that is 0.4.9rc1 or later.

3

What types of software are affected by CVE-2013-2273?

CVE-2013-2273 affects Bitcoin-Qt and bitcoind versions prior to 0.4.9rc1.

4

What kind of information can be exposed due to CVE-2013-2273?

CVE-2013-2273 may allow remote attackers to obtain potentially sensitive information about returned change.

5

Is there any potential for exploit regarding CVE-2013-2273?

Yes, the vulnerability may be exploited due to predictable outputs impacting the privacy of transactions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203