Process crash via unhandled invalid-upgrade socket error
Published Nov 22, 2022 · Updated Apr 22, 2025
Uncaught exception in Engine.IO before 3.6.1 and 4.0.0 through 6.2.0 allows remote authenticated users to crash Node.js. The invalid-upgrade timeout calls socket.end() without an error listener, so an HTTP/2 upgrade reset emits an unhandled ECONNRESET. A reachable Engine.IO server and low-privileged access are required; successful requests terminate the hosting process and interrupt its service.
Summary
What happened
Uncaught exception in Engine.IO before 3.6.1 and 4.0.0 through 6.2.0 allows remote authenticated users to crash Node.js. The invalid-upgrade timeout calls socket.end() without an error listener, so an HTTP/2 upgrade reset emits an unhandled ECONNRESET. A reachable Engine.IO server and low-privileged access are required; successful requests terminate the hosting process and interrupt its service.
The record
- CVE
- CVE-2022-41940
- Published
- Nov 22, 2022
- Updated
- Apr 22, 2025
- Vendor
- Socket.IO
- Product
- Engine.IO
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.6.1
- Affected versionversion=>= 4.0.0, < 6.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo