CVE-2022-21676
Summary
| CVE | CVE-2022-21676 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-01-12 19:15:00 UTC |
| Updated | 2023-06-27 19:03:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-755
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Release 4.1.2 · socketio/engine.io · GitHub | MISC | github.com | |
| Release 5.2.1 · socketio/engine.io · GitHub | MISC | github.com | |
| Uncaught Exception in engine.io · Advisory · socketio/engine.io · GitHub | CONFIRM | github.com | |
| fix: properly handle invalid data sent by a malicious websocket client · socketio/engine.io@66f889f · GitHub | MISC | github.com | |
| fix: properly handle invalid data sent by a malicious websocket client · socketio/engine.io@a70800d · GitHub | MISC | github.com | |
| Release 6.1.1 · socketio/engine.io · GitHub | MISC | github.com | |
| fix: properly handle invalid data sent by a malicious websocket client · socketio/engine.io@c0e194d · GitHub | MISC | github.com | |
| CVE-2022-21676 NPM Vulnerability in NetApp Products | NetApp Product Security | CONFIRM | security.netapp.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.