npm · socket.io-parser
Socket.IO: Zero-attachment Memory Exhaustion
A specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, which can be exploited to make the server run out of memory.
| Version range | Used by | Fixed version |
|---|---|---|
>=4.0.0 <4.2.7 |
socket.io@4.x and socket.io-client@4.x |
4.2.7 |
>=3.4.0 <3.4.5 |
socket.io@2.x |
3.4.5 |
<3.3.6 |
socket.io-client@2.x |
3.3.6 |
There is no known workaround except upgrading to a safe version.
If you have any questions or comments about this advisory:
Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.
Check my repoSources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.