CVE-2016-10518

N/A
Published: May 31, 2018 at 08:00 PM UTC
Updated: June 17, 2026 at 12:39 AM UTC
1 product affected across 1 vendorWs

Using ws node module by HackerOne?

Get instant alerts when new vulnerabilities affect ws node module - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.0.1<= 1.0.0
Affected range stops below 1.0.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_MISCPatchThird Party Advisory
https://gist.github.com/c0nrad/e92005446c480707a74a
x_refsource_MISCRelease NotesThird Party Advisory
https://github.com/websockets/ws/releases/tag/1.0.1
x_refsource_MISCThird Party Advisory
https://nodesecurity.io/advisories/67

CVSS

Confidentiality
PARTIAL
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-201CWE-119

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card