CVE-2016-10518
published 2018-05-31CVE-2016-10518: A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping…
PriorityP339high7.5CVSS 3.0
AVNACLPRNUINSUCHINAN
EPSS
2.02%
78.5th percentile
A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | node-ws | < node-ws 1.0.1+ds1.e6ddaae4-1 (bookworm) | node-ws 1.0.1+ds1.e6ddaae4-1 (bookworm) |
| hackerone | ws_node_module | <= 1.0.0 | — |
| ws_project | ws | < 1.0.1 | 1.0.1 |
| ws_project | ws | >= 0 < 1.0.1 | 1.0.1 |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv7.5HIGH
vendor_debian7.5LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Remote Memory Disclosure in ws
ghsa·2019-02-18
CVE-2016-10518 [LOW] CWE-201 Remote Memory Disclosure in ws
Remote Memory Disclosure in ws
Versions of `ws` prior to 1.0.1 are affected by a remote memory disclosure vulnerability.
In certain rare circumstances, applications which allow users to control the arguments of a `client.ping()` call will cause `ws` to send the contents of an allocated but non-zero-filled buffer to the server. This may disclose sensitive information that still exists in memory after previous use of the memory for other tasks.
## Proof of Concept
```
var ws = require('ws')
var server = new ws.Server({ port: 9000 })
var client = new ws('ws://localhost:9000')
client.on('open', function () {
console.log('open')
client.ping(50) // this sends a non-zeroed buffer of 50 bytes
client.on('pong', function (data) {
console.log('got pong')
console.log(data) // Data from the clie
OSV
Remote Memory Disclosure in ws
osv·2019-02-18
CVE-2016-10518 [LOW] Remote Memory Disclosure in ws
Remote Memory Disclosure in ws
Versions of `ws` prior to 1.0.1 are affected by a remote memory disclosure vulnerability.
In certain rare circumstances, applications which allow users to control the arguments of a `client.ping()` call will cause `ws` to send the contents of an allocated but non-zero-filled buffer to the server. This may disclose sensitive information that still exists in memory after previous use of the memory for other tasks.
## Proof of Concept
```
var ws = require('ws')
var server = new ws.Server({ port: 9000 })
var client = new ws('ws://localhost:9000')
client.on('open', function () {
console.log('open')
client.ping(50) // this sends a non-zeroed buffer of 50 bytes
client.on('pong', function (data) {
console.log('got pong')
console.log(data) // Data from the clie
OSV
CVE-2016-10518: A vulnerability was found in the ping functionality of the ws module before 1
osv·2018-05-31·CVSS 7.5
CVE-2016-10518 [HIGH] CVE-2016-10518: A vulnerability was found in the ping functionality of the ws module before 1
A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.
Debian
CVE-2016-10518: node-ws - A vulnerability was found in the ping functionality of the ws module before 1.0....
vendor_debian·2016·CVSS 7.5
CVE-2016-10518 [HIGH] CVE-2016-10518: node-ws - A vulnerability was found in the ping functionality of the ws module before 1.0....
A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.
Scope: local
bookworm: resolved (fixed in 1.0.1+ds1.e6ddaae4-1)
bullseye: resolved (fixed in 1.0.1+ds1.e6ddaae4-1)
forky: resolved (fixed in 1.0.1+ds1.e6ddaae4-1)
sid: resolved (fixed in 1.0.1+ds1.e6
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2018-05-31
Published