CVE-2016-10519
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencebittorrent-dht before 5.1.3 contains an information disclosure vulnerability where a remote attacker can send a specific series of DHT messages to a listening peer and cause it to leak internal memory contents. This appears to be a protocol-level flaw where crafted message sequences trigger unintended memory reads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify bittorrent-dht package versionRun 'npm list bittorrent-dht' in your project directory, or check your package.json dependencies for the bittorrent-dht version numberAffected if The installed version is less than 5.1.3 (e.g., 5.1.2, 5.1.1, 5.0.0, etc.)
-
Confirm DHT module is in useSearch your codebase for require('bittorrent-dht') or imports of the bittorrent-dht module, and check if your application creates a DHT server or client instanceAffected if Your application actively uses the bittorrent-dht module
-
Verify DHT listener network bindingCheck your application configuration or code for DHT server setup - look for .listen() calls on the DHT instance and whether it binds to a wildcard address (0.0.0.0) or a specific external IP rather than localhost (127.0.0.1)Affected if The DHT listener binds to a non-localhost address (0.0.0.0 or external IP) making it network-accessible
-
Assess network exposure of DHT portRun 'netstat -tlnp' or 'ss -tlnp' to list listening ports, and identify which ports your DHT service uses (typically UDP port 6881 or configured port). Verify whether these ports are accessible from untrusted networksAffected if The DHT port is exposed to untrusted network interfaces or the public internet
You are affected if you have bittorrent-dht version below 5.1.3 AND your DHT listener is accessible from remote, untrusted peers on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.1.3
Upgrade bittorrent-dht to version 5.1.3 or later. If immediate upgrading is not feasible, restrict network accessibility of DHT listeners to trusted peers only.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10519 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data