GHSA-77G4-36JP-5V3M
Vulnerability from github – Published: 2020-09-01 15:22 – Updated: 2020-08-31 18:09
VLAI?
Summary
Remote Memory Disclosure in bittorrent-dht
Details
Versions of bittorrent-dht prior to 5.1.3 are affected by a remote memory disclosure vulnerability. This vulnerability allows an attacker to send a specific series of of messages to a listening peer and get it to reveal internal memory.
There are two mitigating factors here, that slightly reduce the impact of this vulnerability:
- Any modern kernel will zero out new memory pages before handing them off to a process. This means that only memory previously used and deallocated by the node process can be leaked.
- Node.js manages Buffers by creating a few large internal SlowBuffers, and slicing them up into smaller Buffers which are made accessible in JS. They are not stored on V8's heap, because garbage collection would interfere. The result is that only memory that has been previously allocated as a Buffer can be leaked.
Recommendation
Update to version 5.1.3 or later.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "bittorrent-dht"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.1.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2016-10519"
],
"database_specific": {
"cwe_ids": [
"CWE-201"
],
"github_reviewed": true,
"github_reviewed_at": "2020-08-31T18:09:58Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "Versions of `bittorrent-dht` prior to 5.1.3 are affected by a remote memory disclosure vulnerability. This vulnerability allows an attacker to send a specific series of of messages to a listening peer and get it to reveal internal memory.\n\n\nThere are two mitigating factors here, that slightly reduce the impact of this vulnerability:\n\n1. Any modern kernel will zero out new memory pages before handing them off to a process. This means that only memory previously used and deallocated by the node process can be leaked.\n1. Node.js manages Buffers by creating a few large internal SlowBuffers, and slicing them up into smaller Buffers which are made accessible in JS. They are not stored on V8\u0027s heap, because garbage collection would interfere. The result is that only memory that has been previously allocated as a Buffer can be leaked.\n\n\n## Recommendation\n\nUpdate to version 5.1.3 or later.",
"id": "GHSA-77g4-36jp-5v3m",
"modified": "2020-08-31T18:09:58Z",
"published": "2020-09-01T15:22:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10519"
},
{
"type": "WEB",
"url": "https://github.com/feross/bittorrent-dht/issues/87"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/68"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Remote Memory Disclosure in bittorrent-dht"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…