First published: Tue Nov 22 2022(Updated: )
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, including those who uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Socket Engine.io | <3.6.1 | |
Socket Engine.io | >=4.0.0<6.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-41940 is a vulnerability in the Engine.IO communication layer for Socket.IO, where a specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, leading to the termination of the Node.js process.
The severity of CVE-2022-41940 is high, with a CVSS score of 6.5.
Engine.IO versions up to, but excluding, 3.6.1 and versions up to, but excluding, 6.2.1 are affected by CVE-2022-41940.
To fix CVE-2022-41940, update your Engine.IO package to version 3.6.1 or higher if using versions prior to 6.2.1, or update to version 6.2.1 or higher if using versions 4.0.0 and higher.
Yes, you can find additional references for CVE-2022-41940 at the following links: [GitHub Commit 1](https://github.com/socketio/engine.io/commit/83c4071af871fc188298d7d591e95670bf9f9085), [GitHub Commit 2](https://github.com/socketio/engine.io/commit/425e833ab13373edf1dd5a0706f07100db14e3c6), [GitHub Security Advisory](https://github.com/socketio/engine.io/security/advisories/GHSA-r7qp-cfhv-p84w).