# CVE-2020-6861: Other in n/a

> A local attacker can extract the master spending key from a connected Ledger device by sending crafted messages to the Monero app.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hpg2-wgv6-vgm5

## What is CVE-2020-6861?

CVE-2020-6861 is a medium-severity vulnerability in n/a, published on 6 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flawed protocol design in the Ledger Monero app before 1.5.1 for Ledger Nano and Ledger S devices allows a local attacker to extract the master spending key by sending crafted messages to this app selected on a PIN-entered Ledger connected to a host PC.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2020-6861?

It affects 1 product.


Products: Ledger Monero.

## How do I fix CVE-2020-6861?

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

## Is CVE-2020-6861 being exploited?

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

Public exploit code:

- PoC repository for CVE-2020-6861: Ledger Monero App Spend key Extraction (github_poc): https://github.com/ph4r05/ledger-app-monero-1.42-vuln

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6861 and fix it if it is affected.

What it is: CVE-2020-6861 is a medium-severity vulnerability in n/a, published on 6 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6861 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-2020-6861/ (Markdown: https://insights.sbomify.com/CVE-2020-6861/index.md)
```

## Sources

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

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