# CVE-2023-27892: Memory corruption in n/a

> Attackers with physical access to an unlocked KeepKey wallet can exploit buffer overflows to extract the BIP39 mnemonic or crash the device.

- **Severity:** Low 3.8 (`CVSS:3.1/AC:H/AV:P/A:N/C:H/I:N/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-76qj-23pr-3333

## What is CVE-2023-27892?

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.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-27892?

It affects 1 product.


Products: Shapeshift Keepkey Firmware.

## How do I fix CVE-2023-27892?

No fix has been published for CVE-2023-27892 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27892 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27892 exists.

## Other vulnerabilities in n/a

- [CVE-2021-31616](https://insights.sbomify.com/CVE-2021-31616/): Memory corruption in n/a (high 8.8)
- [CVE-2019-18672](https://insights.sbomify.com/CVE-2019-18672/): Other in n/a (high 7.5)
- [CVE-2018-6875](https://insights.sbomify.com/CVE-2018-6875/): Information disclosure in n/a (high 7.5)
- [CVE-2019-14355](https://insights.sbomify.com/CVE-2019-14355/): Information disclosure in n/a (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27892 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27892 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27892/ (Markdown: https://insights.sbomify.com/CVE-2023-27892/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27892
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27892
- OSV: https://osv.dev/vulnerability/CVE-2023-27892

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27892/
Summaries are generated and may contain mistakes; the official description above is the record.