Ws Node Module

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:hackerone:ws_node_module:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorHackerone (9b72fff1-532f-502a-8030-14fc4a21dd17)
ProductWs Node Module (38682223-f531-57df-969d-da042ba6b5bb)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2016-10542 vulnerable 2026-06-08 05:07:25.289892 Details available
ws is a "simple to use, blazing fast and thoroughly tested websocket client, server and console for node.js, up-to-date against RFC-6455". By sending an overly long websocket payload to a `ws` server, it is possible to crash the node process. This affects ws 1.1.0 and earlier.
Published: 2018-05-31T20:00:00.000Z
Updated: 2024-09-17T04:03:37.757Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-10518 vulnerable 2026-06-08 05:07:25.239186 Details available
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: 2018-05-31T20:00:00.000Z
Updated: 2024-09-17T02:57:19.095Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.