First published: Wed Jan 12 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 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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Socket Engine.io | >=4.0.0<4.1.2 | |
Socket Engine.io | >=5.0.0<5.2.1 | |
Socket Engine.io | >=6.0.0<6.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-21676 is a vulnerability in Engine.IO, a transport-based bi-directional communication layer for Socket.IO, where a specially crafted HTTP request can cause an uncaught exception, leading to the termination of the Node.js process.
CVE-2022-21676 impacts all users of Socket.Engine.IO and Node.js versions between 4.0.0 and 4.1.2, versions between 5.0.0 and 5.2.1, and versions between 6.0.0 and 6.1.1.
CVE-2022-21676 has a severity rating of 7.5 (high).
To fix CVE-2022-21676, users should update to the latest versions of Socket.Engine.IO and Node.js.
More information about CVE-2022-21676 can be found in the references provided by Socket.Engine.IO on their GitHub page.