Socket.IO: Prototype Pollution via Unsafe Client Session Lookup
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 |
|
||||||
| @socket.io | cluster-engine | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Socket | Cluster-engine |
|
||||||||
| Socket | Socket.io |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wfpm-5gcm-94cg | Socket.IO: Prototype Pollution via Unsafe Client Session Lookup |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.382% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Socket
Socket cluster-engine Socket socket.io |
|
| Vendors & Products |
Socket
Socket cluster-engine Socket socket.io |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1. | |
| Title | Socket.IO: Prototype Pollution via Unsafe Client Session Lookup | |
| Weaknesses | CWE-1321 CWE-20 |
|
| References |
| |
| Metrics |
cvssV3_1
|