Process crash via mishandled WebSocket handshake errors
Published Jan 12, 2022 · Updated Apr 23, 2025
Uncaught exceptions in affected Engine.IO 4.x through 6.x releases allow remote attackers to crash the Node.js server via crafted HTTP requests. During WebSocket handshakes, server.js removes its upgrade-error listener before calling handshake, so invalid frame data raises an unhandled RangeError. No authentication or user interaction is required, and each successful request terminates the hosting Node.js process rather than affecting confidentiality or integrity.
Summary
What happened
Uncaught exceptions in affected Engine.IO 4.x through 6.x releases allow remote attackers to crash the Node.js server via crafted HTTP requests. During WebSocket handshakes, server.js removes its upgrade-error listener before calling handshake, so invalid frame data raises an unhandled RangeError. No authentication or user interaction is required, and each successful request terminates the hosting Node.js process rather than affecting confidentiality or integrity.
The record
- CVE
- CVE-2022-21676
- Published
- Jan 12, 2022
- Updated
- Apr 23, 2025
- Vendor
- Socket.IO
- Product
- Engine.IO
- Classifications
- CWE-248, CWE-755, CWE-754, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=>= 4.0.0, < 4.1.2
- Affected versionversion=>= 5.0.0, < 5.2.1
- Affected versionversion=>= 6.0.0, < 6.1.1
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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