Buffer overflow in HackerOne Ws Node Module
CVE-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 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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.019, 80.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- HackerOne Ws Node Module — versions <= 1.0.0
- Ws Project
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/websockets/ws/releases/tag/1.0.1 (Third Party Advisory, Release Notes)
- nodesecurity.io/advisories/67 (Third Party Advisory)
- gist.github.com/c0nrad/e92005446c480707a74a (Patch, Third Party Advisory)