CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1CVE-2021-3845 – External Control of File Name or Path in netristv/ws-scrcpy
https://notcve.org/view.php?id=CVE-2021-3845
ws-scrcpy is vulnerable to External Control of File Name or Path ws-scrcpy es vulnerable al Control Externo del Nombre o la Ruta del Archivo • https://github.com/netristv/ws-scrcpy/commit/e83cf65438bef83a3503b25358bba97bcc156fef https://huntr.dev/bounties/dc7fc98f-4f4f-440a-b6f6-124a56ea36ef • CWE-73: External Control of File Name or Path CWE-610: Externally Controlled Reference to a Resource in Another Sphere •
CVSS: 5.3EPSS: 0%CPEs: 3EXPL: 1CVE-2021-32640 – ReDoS in Sec-Websocket-Protocol header
https://notcve.org/view.php?id=CVE-2021-32640
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. ws es una biblioteca de servidor y cliente WebSocket de código abierto para Node.js. Un valor especialmente diseñado del encabezado "Sec-Websocket-Protocol" puede ser usado para ralentizar significativamente un servidor ws. • https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff https://github.com/websockets/ws/security/advisories/GHSA-6fc8-4gx4-v693 https://lists.apache.org/thread.html/rdfa7b6253c4d6271e31566ecd5f30b7ce1b8fb2c89d52b8c4e0f4e30%40%3Ccommits.tinkerpop.apache.org%3E https://security.netapp.com/advisory/ntap-20210706-0005 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-35896
https://notcve.org/view.php?id=CVE-2020-35896
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack. Se detectó un problema en la crate WS hasta el 25-09-2020 para Rust. El búfer de salida no está apropiadamente limitado, conllevando un ataque de consumo de memoria remoto. • https://rustsec.org/advisories/RUSTSEC-2020-0043.html • CWE-770: Allocation of Resources Without Limits or Throttling •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2016-10542
https://notcve.org/view.php?id=CVE-2016-10542
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: 0CVE-2016-10518
https://notcve.org/view.php?id=CVE-2016-10518
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 •