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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.02%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 2.02% probability · 80th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-201, CWE-119
- Affected
- ws project/ws
- Source
- support@hackerone.com
References
- https://gist.github.com/c0nrad/e92005446c480707a74aPatch, Third Party Advisory
- https://github.com/websockets/ws/releases/tag/1.0.1Release Notes, Third Party Advisory
- https://nodesecurity.io/advisories/67Third Party Advisory
- https://gist.github.com/c0nrad/e92005446c480707a74aPatch, Third Party Advisory
- https://github.com/websockets/ws/releases/tag/1.0.1Release Notes, Third Party Advisory
- https://nodesecurity.io/advisories/67Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.