{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15947 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-15947 is a high-severity vulnerability in Bitcoin Bitcoin Core, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15947 and fix it if it is affected.\n\nWhat it is: CVE-2019-15947 is a high-severity vulnerability in Bitcoin Bitcoin Core, published on 5 Sep 2019. 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-2019-15947 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-2019-15947/ (Markdown: https://insights.sbomify.com/CVE-2019-15947/index.md)","id":"CVE-2019-15947","markdown":"https://insights.sbomify.com/CVE-2019-15947/index.md","name":"CVE-2019-15947","record":{"aliases":["GHSA-g4g7-v7q6-4xw8"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin Core client","requires_auth":"none","summary":"An attacker can recover private keys from unencrypted memory dumps if a user mishandles core files generated after a Bitcoin Core crash.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin_core","vendor":"bitcoin"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"In Bitcoin Core 0.18.0, bitcoin-qt stores wallet.dat data unencrypted in memory. Upon a crash, it may dump a core file. If a user were to mishandle a core file, an attacker can reconstruct the user's wallet.dat file, including their private keys, via a grep \"6231 0500\" command.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2019-15947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"bitcoin:bitcoin_core","products":["bitcoin:bitcoin_core"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-15948"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-15946"},"products":["n/a"],"published":"2019-09-05","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-08-05","vendors":["n/a"]},"summary":"An attacker can recover private keys from unencrypted memory dumps if a user mishandles core files generated after a Bitcoin Core crash.","url":"https://insights.sbomify.com/CVE-2019-15947/"}