# CVE-2021-31616: Memory corruption in n/a

> A stack buffer overflow in KeepKey firmware allows remote code execution via crafted WebUSB messages, requiring a firmware upgrade.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jjq4-78fg-7j7h

## What is CVE-2021-31616?

CVE-2021-31616 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insufficient length checks in the ShapeShift KeepKey hardware wallet firmware before 7.1.0 allow a stack buffer overflow via crafted messages. The overflow in ethereum_extractThorchainSwapData() in ethereum.c can circumvent stack protections and lead to code execution. The vulnerable interface is reachable remotely over WebUSB.

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

## Which versions are affected by CVE-2021-31616?

It affects 1 product.


Products: Shapeshift Keepkey Firmware.

## How do I fix CVE-2021-31616?

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

## Is CVE-2021-31616 being exploited?

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

## Other vulnerabilities in n/a

- [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-2023-27892](https://insights.sbomify.com/CVE-2023-27892/): Memory corruption in n/a (low 3.8)
- [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-2021-31616 and fix it if it is affected.

What it is: CVE-2021-31616 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-31616 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-2021-31616/ (Markdown: https://insights.sbomify.com/CVE-2021-31616/index.md)
```

## Sources

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

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