Approved changes feed: RSS · Atom
cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:*part: a version: * update: *
| Vendor | Ws Project (5a380f5c-9de3-54a8-b226-f9c7792bd31f) |
|---|---|
| Product | Ws (c80c13b4-01af-5db5-9d67-6a9fc593e451) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/node-ws |
purl2cpe | 2026-06-01 10:11:04.818972 |
pkg:deb/ubuntu/node-ws |
purl2cpe | 2026-06-01 10:11:04.818974 |
pkg:github/websockets/ws |
purl2cpe | 2026-06-01 10:11:04.818975 |
pkg:maven/org.webjars.npm/ws |
purl2cpe | 2026-06-01 10:11:04.818976 |
pkg:npm/ws |
purl2cpe | 2026-06-01 10:11:04.818978 |
pkg:rpm/fedora/nodejs-ws |
purl2cpe | 2026-06-01 10:11:04.818979 |
pkg:rpm/opensuse/nodejs-ws |
purl2cpe | 2026-06-01 10:11:04.818981 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-45736 |
vulnerable | 2026-06-08 08:05:11.852237 |
ws: Uninitialized memory disclosure
MEDIUM (4.4)
ws is an open source WebSocket client and server for Node.js. Prior to 8.20.1, the websocket.close() implementation is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument. This vulnerability is fixed in 8.20.1.
Published: 2026-05-15T14:53:57.263Z
Updated: 2026-09-11T12:09:09.123Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32640 |
vulnerable | 2026-06-08 05:32:07.733445 |
ReDoS in Sec-Websocket-Protocol header
MEDIUM (5.3)
ws is an open source WebSocket client and server library for Node.js. A specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server. The vulnerability has been fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff). In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.
Published: 2021-05-25T18:25:09.000Z
Updated: 2024-08-03T23:25:31.019Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-10542 |
vulnerable | 2026-06-08 05:07:25.289931 |
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 |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-10518 |
vulnerable | 2026-06-08 05:07:25.239740 |
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 |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.