2 results (0.022 seconds)

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

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. ws es un "cliente, servidor y consola websocket para Node.js fácil de usar, increíblemente rápido y testado en profundidad, actualizado contra RFC-6455". Mediante el envío de una carga útil websocket demasiado larga a un servidor "ws", es posible provocar el cierre inesperado del proceso node. Esto afecta a ws en versiones 1.1.0 y anteriores. • https://github.com/nodejs/node/issues/7388 https://nodesecurity.io/advisories/120 • CWE-20: Improper Input Validation CWE-400: Uncontrolled Resource Consumption •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

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. Se ha encontrado una vulnerabilidad en la funcionalidad ping del módulo ws en versiones anteriores a la 1.0.0 que permite que los clientes asignen memoria mediante el envío de un frame ping. • https://gist.github.com/c0nrad/e92005446c480707a74a https://github.com/websockets/ws/releases/tag/1.0.1 https://nodesecurity.io/advisories/67 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer CWE-201: Insertion of Sensitive Information Into Sent Data •