Socket.IO: Engine.IO Protocol Revision Mismatch DoS

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

• engine.io 6.6.10Fixed version · GitHub Advisories · npm package engine.io: upgrade to 6.6.10 or later (affected >= 6.6.0, < 6.6.10)

[ Packages ]Affected open-source packages

• engine.io npmAffected >= 6.6.0, < 6.6.10 · fixed in 6.6.10 · GHSA-2gc4-cqfq-p2gv

[ References ]References

• github.com/socketio/socket.io/commit/86db1fc3db2cd315a065d64c4e48918ccf9b4729
• github.com/socketio/socket.io/releases/tag/engine.io@6.6.10
• github.com/socketio/socket.io/security/advisories/GHSA-2gc4-cqfq-p2gv