{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-3219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-3219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-3219 is a medium-severity vulnerability in Bitcoin Bitcoin Core, published on 1 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-3219 and fix it if it is affected.\n\nWhat it is: CVE-2013-3219 is a medium-severity vulnerability in Bitcoin Bitcoin Core, published on 1 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-3219 in the wild and no public exploit code.\n\nAffected product: Bitcoin Bitcoin Core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2013-3219/ (Markdown: https://insights.sbomify.com/CVE-2013-3219/index.md)","id":"CVE-2013-3219","markdown":"https://insights.sbomify.com/CVE-2013-3219/index.md","name":"CVE-2013-3219","record":{"aliases":["GHSA-8mqp-6q8h-2r3q"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin client","requires_auth":"none","summary":"Remote attackers can bypass block protocol rules to conduct double-spending attacks via large blocks triggering incorrect database locking.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin_core","vendor":"bitcoin"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Business logic in n/a","id":"CVE-2013-3219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"bitcoin:bitcoin_core","products":["bitcoin:bitcoin_core"],"type":"business_logic","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2013-3220"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2013-3215"},"products":["n/a"],"published":"2013-08-01","related":[{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2025-46597","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-54604","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-54605","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-25220","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2024-52912","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-52914","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-52915","kev_date_added":null,"published":"2024-11-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can bypass block protocol rules to conduct double-spending attacks via large blocks triggering incorrect database locking.","url":"https://insights.sbomify.com/CVE-2013-3219/"}