CVE-2013-3219: Medium severity Bitcoin Bitcoin Core vulnerability

Published Aug 1, 2013
·
Updated

bitcoind and Bitcoin-Qt 0.8.x before 0.8.1 do not enforce a certain block protocol rule, which allows remote attackers to bypass intended access restrictions and conduct double-spending attacks via a large block that triggers incorrect Berkeley DB locking in older product versions.

Affected Software

2 affected components
Bitcoin Bitcoin Core=0.8.0
Bitcoin Bitcoin Core=0.8.0-rc1

Event History

Aug 1, 2013
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
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-3219?

CVE-2013-3219 is classified as a high severity vulnerability due to its potential for allowing remote attackers to conduct double-spending attacks.

2

How do I fix CVE-2013-3219?

To fix CVE-2013-3219, upgrade to Bitcoin Core version 0.8.1 or later, which enforces the necessary block protocol rules.

3

What types of systems are affected by CVE-2013-3219?

CVE-2013-3219 affects Bitcoin Core versions 0.8.0 and 0.8.0-rc1, allowing exploitation on those specific versions.

4

What is the impact of exploiting CVE-2013-3219?

Exploiting CVE-2013-3219 can enable attackers to bypass access restrictions, leading to double-spending risks in Bitcoin transactions.

5

Who is at risk from CVE-2013-3219?

Users running vulnerable versions of Bitcoin Core are at risk from CVE-2013-3219 and should consider updating their software.

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