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.
Remediation
References
https://gist.github.com/c0nrad/e92005446c480707a74a
https://github.com/websockets/ws/releases/tag/1.0.1
https://nodesecurity.io/advisories/67
Related Vulnerabilities
CVE-2023-40167 Vulnerability in maven package org.eclipse.jetty:jetty-http
CVE-2023-30541 Vulnerability in npm package @openzeppelin/contracts-upgradeable
CVE-2017-5661 Vulnerability in maven package org.apache.xmlgraphics:fop
CVE-2016-10518 Vulnerability in npm package ws
CVE-2021-22696 Vulnerability in maven package org.apache.cxf:cxf-rt-rs-security-oauth2