Socket.IO
Socket.IO: Engine.IO Protocol Revision Mismatch DoS
Socket.IO enables bidirectional and low-latency communication for every platform. From Engine.IO 6.6.0 until 6.6.10, a transport upgrade can independently derive an Engine.IO protocol revision from the upgrade request instead of enforcing the revision stored on the existing session. A malicious client can establish a valid session and send an upgrade request with a different or omitted EIO query parameter, attaching a transport with incompatible parser and heartbeat behavior. A crafted heartbeat packet can then trigger an uncaught exception and terminate the Node.js process, including when Engine.IO v3 compatibility is disabled because an omitted EIO value is interpreted as revision 3 on the affected path. This issue is fixed in Engine.IO 6.6.10.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.6.0, < 6.6.10
Fixed in 6.6.10
Mitigation
Upgrade socket.io to 6.6.10 or later.
References
- Vendor advisory github.com/socketio/socket.io/security/advisor…
- Patch github.com/socketio/socket.io/commit/86db1fc3d…
- Release notes github.com/socketio/socket.io/releases/tag/eng…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.