socket.io-parser
Affected
- introduced
4.0.4, fixed4.2.3(semver)
Fixed versions
4.2.3
Fix
- Fixed version
4.2.3npm install [email protected]
Advisory
Also known as: CVE-2023-32695
Insufficient validation when decoding a Socket.IO packet
Impact
A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.
TypeError: Cannot convert object to primitive value
at Socket.emit (node:events:507:25)
at .../node_modules/socket.io/lib/socket.js:531:14
Patches
A fix has been released today (2023/05/22):
[email protected][email protected]Another fix has been released for the 3.3.x branch:
| socket.io version | socket.io-parser version | Needs minor update? |
|---------------------|---------------------------------------------------------------------------------------------------------|--------------------------------------|
| 4.5.2...latest | ~4.2.0 (ref) | npm audit fix should be sufficient |
| 4.1.3...4.5.1 | ~4.1.1 (ref) | Please upgrade to [email protected] |
| 3.0.5...4.1.2 | ~4.0.3 (ref) | Please upgrade to [email protected] |
| 3.0.0...3.0.4 | ~4.0.1 (ref) | Please upgrade to [email protected] |
| 2.3.0...2.5.0 | ~3.4.0 (ref) | npm audit fix should be sufficient |
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
Thanks to @rafax00 for the responsible disclosure.
Medium Basis: The source's own band: MODERATE
4.0.4, fixed 4.2.3 (semver)4.2.3
4.2.3npm install [email protected]3.4.0, fixed 3.4.3 (semver)3.4.3
3.4.3npm install [email protected]0, fixed 3.3.4 (semver)3.3.4
3.3.4npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0