{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27892 exists.","fix":"No fix has been published for CVE-2023-27892 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-27892 is a low-severity memory corruption vulnerability in n/a, published on 2 May 2023. 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-2023-27892 and fix it if it is affected.\n\nWhat it is: CVE-2023-27892 is a low-severity memory corruption vulnerability in n/a, published on 2 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27892 exists.\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-2023-27892/ (Markdown: https://insights.sbomify.com/CVE-2023-27892/index.md)","id":"CVE-2023-27892","markdown":"https://insights.sbomify.com/CVE-2023-27892/index.md","name":"CVE-2023-27892","record":{"aliases":["GHSA-76qj-23pr-3333"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"KeepKey hardware wallet","requires_auth":"high_privilege","summary":"Attackers with physical access to an unlocked KeepKey wallet can exploit buffer overflows to extract the BIP39 mnemonic or crash the device.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"keepkey_firmware","vendor":"shapeshift"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AC:H/AV:P/A:N/C:H/I:N/PR:H/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Insufficient length checks in the ShapeShift KeepKey hardware wallet firmware before 7.7.0 allow a global buffer overflow via crafted messages. Flaws in cf_confirmExecTx() in ethereum_contracts.c can be used to reveal arbitrary microcontroller memory on the device screen or crash the device. With physical access to a PIN-unlocked device, attackers can extract the BIP39 mnemonic secret from the hardware wallet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2023-27892","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Arbitrary Code Execution in SAP Solution Manager and ABAP managed systems (ST-PI)","id":"CVE-2023-27893"},"packages":[],"prev":{"headline":"Insufficient Session Expiration in pretix","id":"CVE-2023-27891"},"products":["n/a"],"published":"2023-05-02","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2021-31616","kev_date_added":null,"published":"2021-05-06"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2019-18672","kev_date_added":null,"published":"2019-12-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-6875","kev_date_added":null,"published":"2018-03-14"},{"cvss_score":2.4,"headline":"Information disclosure in n/a","id":"CVE-2019-14355","kev_date_added":null,"published":"2019-08-10"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["n/a"]},"summary":"Attackers with physical access to an unlocked KeepKey wallet can exploit buffer overflows to extract the BIP39 mnemonic or crash the device.","url":"https://insights.sbomify.com/CVE-2023-27892/"}