Quick answers
- Is CVE-2022-41940 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-41940 being exploited in the wild.
- How severe is CVE-2022-41940?
- Low severity, with a CVSS score of 3.1, published 21 November 2022.
- Which products and versions are affected?
- engine.io (npm) SEMVER:introduced=0,fixed=3.6.1.
- Is there a fix for CVE-2022-41940?
- Yes. engine.io (npm): upgrade to 3.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-41940 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-41940?
- Check whether you run engine.io (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- engine.io (npm): upgrade to 3.6.1 or later
npm install engine.io@3.6.1
Technical details
The vulnerability is an unhandled exception (CWE-248) triggered by specially crafted HTTP requests that cause an ECONNRESET error on the TCP socket. The error occurs in Engine.IO's socket handling code when processing connection stream data, and because the error event is not properly caught, it propagates as an uncaught exception that terminates the Node.js process. The attack requires network access to the Engine.IO server but no authentication. A fix was released on 2022-11-20 with Engine.IO versions 3.6.1 and 6.2.1, and Socket.IO users should upgrade accordingly.
Affected products
- Socket.io Engine.IO < 3.6.1, >= 4.0.0 and <= 6.2.1
- Socket.io Socket.IO 2.4.x and below, 2.5.0, 3.0.x, 3.1.x, 4.0.x, 4.1.x, 4.2.x, 4.3.x, 4.4.x
Identifiers
- CVE-2022-41940
- GHSA-r7qp-cfhv-p84w
Timeline
- 2022-11-20: disclosed: Advisory published
- 2022-11-20: patched: Patches released: Engine.IO 3.6.1 and 6.2.1