Socket.IO: Engine.IO Protocol Revision Mismatch DoS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| socketio | socket.io | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Socket | Socket.io |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2gc4-cqfq-p2gv | Socket.IO: Engine.IO Protocol Revision Mismatch DoS |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.576% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Socket
Socket socket.io |
|
| Vendors & Products |
Socket
Socket socket.io |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Socket.IO: Engine.IO Protocol Revision Mismatch DoS | |
| Weaknesses | CWE-248 | |
| References |
| |
| Metrics |
cvssV3_1
|