# CVE-2016-10519: Remote Memory Disclosure in bittorrent-dht

> An attacker can send specific messages to a listening peer to reveal internal memory contents in the bittorrent-dht library.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-77g4-36jp-5v3m

## What is CVE-2016-10519?

CVE-2016-10519 is a high-severity vulnerability in HackerOne bittorrent-dht node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security issue was found in bittorrent-dht before 5.1.3 that allows someone to send a specific series of messages to a listening peer and get it to reveal internal memory.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2016-10519?

2 open source packages ship an affected version, including bittorrent-dht. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bittorrent-dht` | npm | All versions | 5.1.3 |
| `bittorrent-dht` | npm | All versions | 5.1.3 |

Products: Webtorrent Bittorrent-Dht.

## How do I fix CVE-2016-10519?

Upgrade bittorrent-dht to 5.1.3 or later.

## Is CVE-2016-10519 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10519 and fix it if it is affected.

What it is: CVE-2016-10519 is a high-severity vulnerability in HackerOne bittorrent-dht node module, published on 31 May 2018. 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-2016-10519 in the wild and no public exploit code.

Affected packages and fixed versions:
- bittorrent-dht (npm): affected all versions; fixed in 5.1.3
- bittorrent-dht (npm): affected all versions; fixed in 5.1.3

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

## Sources

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

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