socket.io-parser vulnerabilities
socket.io protocol parser
- Registry
- npm
- Latest
- 4.2.7
- License
- MIT
5 known advisories
The latest version, 4.2.7, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
npm install socket.io-parser@4.2.7Security advisories for socket.io-parser
Socket.IO: Zero-attachment Memory Exhaustion
- Affected
- >=4.0.0 <4.2.7 · >=3.4.0 <3.4.5 · <3.3.6
- Fixed in
- 3.3.6, 3.4.5, 4.2.7
socket.io allows an unbounded number of binary attachments
- Affected
- <3.3.5 · >=3.4.0 <3.4.4 · >=4.0.0 <4.2.6
- Fixed in
- 3.3.5, 3.4.4, 4.2.6
Insufficient validation when decoding a Socket.IO packet
- Affected
- >=4.0.4 <4.2.3 · >=3.4.0 <3.4.3 · <3.3.4
- Fixed in
- 3.3.4, 3.4.3, 4.2.3
Insufficient validation when decoding a Socket.IO packet
- Affected
- >=4.0.0 <4.0.5 · >=4.1.0 <4.2.1 · <3.3.3 · >=3.4.0 <3.4.2
- Fixed in
- 3.3.3, 3.4.2, 4.0.5, 4.2.1
Resource exhaustion in socket.io-parser
- Affected
- <3.3.2 · >=3.4.0 <3.4.1
- Fixed in
- 3.3.2, 3.4.1
Which of your client projects still run an old socket.io-parser?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.