Socket.IO
Socket.IO: Prototype Pollution via Unsafe Client Session Lookup
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.1.1
Fixed in 0.1.1
- < 0.1.1
Fixed in 0.1.1
Mitigation
Upgrade socket.io to 0.1.1 or later.
Upgrade cluster-engine to 0.1.1 or later.
References
- Vendor advisory github.com/socketio/socket.io/security/advisor…
- Patch github.com/socketio/socket.io/commit/830e3642e…
- Release notes github.com/socketio/socket.io/releases/tag/@so…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.