Filtered by vendor Socket
Subscribe
Search
Total
4 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2022-21676 | 1 Socket | 1 Engine.io | 2022-06-14 | 5.0 MEDIUM | 7.5 HIGH |
| Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package starting from version `4.0.0`, including those who uses depending packages like `socket.io`. Versions prior to `4.0.0` are not impacted. A fix has been released for each major branch, namely `4.1.2` for the `4.x.x` branch, `5.2.1` for the `5.x.x` branch, and `6.1.1` for the `6.x.x` branch. There is no known workaround except upgrading to a safe version. | |||||
| CVE-2020-36049 | 1 Socket | 1 Socket.io-parser | 2021-07-21 | 5.0 MEDIUM | 7.5 HIGH |
| socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used. | |||||
| CVE-2020-36048 | 1 Socket | 1 Engine.io | 2021-01-12 | 5.0 MEDIUM | 7.5 HIGH |
| Engine.IO before 4.0.0 allows attackers to cause a denial of service (resource consumption) via a POST request to the long polling transport. | |||||
| CVE-2017-16031 | 1 Socket | 1 Socket.io | 2018-07-31 | 5.0 MEDIUM | 7.5 HIGH |
| Socket.io is a realtime application framework that provides communication via websockets. Because socket.io 0.9.6 and earlier depends on `Math.random()` to create socket IDs, the IDs are predictable. An attacker is able to guess the socket ID and gain access to socket.io servers, potentially obtaining sensitive information. | |||||