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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
References 3
https://github.com/socketio/socket.io/commit/830e3642ebb8dc3784eb749b0a004fe2b9…
security-advisories@github.com
https://github.com/socketio/socket.io/releases/tag/@socket.io/cluster-engine@0.…
security-advisories@github.com
https://github.com/socketio/socket.io/security/advisories/GHSA-wfpm-5gcm-94cg
security-advisories@github.com