# CVE-2019-18671: Memory corruption in n/a

> Out-of-bounds write in USB packet handling allows unauthenticated attackers to execute code via WebUSB on ShapeShift KeepKey devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xf55-34cc-4qxw

## What is CVE-2019-18671?

CVE-2019-18671 is a critical memory corruption vulnerability in n/a, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient checks in the USB packet handling of the ShapeShift KeepKey hardware wallet before firmware 6.2.2 allow out-of-bounds writes in the .bss segment via crafted messages. The vulnerability could allow code execution or other forms of impact. It can be triggered by unauthenticated attackers and the interface is reachable via WebUSB.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-18671?

It affects 1 product.


Products: Keepkey Keepkey Firmware.

## How do I fix CVE-2019-18671?

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

## Is CVE-2019-18671 being exploited?

There is no known exploitation of CVE-2019-18671 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-30330](https://insights.sbomify.com/CVE-2022-30330/): Privilege escalation in n/a (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18671 and fix it if it is affected.

What it is: CVE-2019-18671 is a critical memory corruption vulnerability in n/a, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18671 in the wild and no public exploit code.

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-2019-18671/ (Markdown: https://insights.sbomify.com/CVE-2019-18671/index.md)
```

## Sources

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

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