{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-8889 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8889 is a medium-severity vulnerability in n/a, published on 28 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-8889 and fix it if it is affected.\n\nWhat it is: CVE-2016-8889 is a medium-severity vulnerability in n/a, published on 28 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-8889 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-8889/ (Markdown: https://insights.sbomify.com/CVE-2016-8889/index.md)","id":"CVE-2016-8889","markdown":"https://insights.sbomify.com/CVE-2016-8889/index.md","name":"CVE-2016-8889","record":{"aliases":["GHSA-pf2g-289p-wmj9"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bitcoin Knots client","requires_auth":"none","summary":"Attackers with local access can read private keys and wallet passphrases from the debug console history in Bitcoin Knots.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin_knots","vendor":"bitcoin_knots_project"}],"cvss":{"score":6.2,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Bitcoin Knots v0.11.0.ljr20150711 through v0.13.0.knots20160814 (fixed in v0.13.1.knots20161027), the debug console stores sensitive information including private keys and the wallet passphrase in its persistent command history.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2016-8889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2016-8897"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2016-8887"},"products":["n/a"],"published":"2016-10-28","related":[],"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-06","vendors":["n/a"]},"summary":"Attackers with local access can read private keys and wallet passphrases from the debug console history in Bitcoin Knots.","url":"https://insights.sbomify.com/CVE-2016-8889/"}