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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| HackerOne | ws node module | <= 1.0.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | node-ws | 1.0.1+ds1.e6ddaae4-1 | — |
| Debian 13 | node-ws | 1.0.1+ds1.e6ddaae4-1 | — |
| Debian 12 | node-ws | 1.0.1+ds1.e6ddaae4-1 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 16.04 LTS | node-ws | 1.0.1+ds1.e6ddaae4-1 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | ws | < 1.0.1 | 1.0.1 | GHSA-2mhh-w6q8-5hxw |