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 .../nodemodules/socket.io/lib/socket.js:531:14
Patches
A fix has been released today (2023/05/22):
- https://github.com/socketio/socket.io-parser/commit/3b78117bf6ba7e99d7a5cfc1ba54d0477554a7f3, included in socket.io-parser@4.2.3 - https://github.com/socketio/socket.io-parser/commit/2dc3c92622dad113b8676be06f23b1ed46b02ced, included in socket.io-parser@3.4.3
Another fix has been released for the 3.3.x branch:
- https://github.com/socketio/socket.io-parser/commit/ee006607495eca4ec7262ad080dd3a91439a5ba4, included in socket.io-parser@3.3.4
| 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 socket.io@4.6.x | | 3.0.5...4.1.2 | ~4.0.3 (ref) | Please upgrade to socket.io@4.6.x | | 3.0.0...3.0.4 | ~4.0.1 (ref) | Please upgrade to socket.io@4.6.x | | 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:
- Open a discussion here
Thanks to @rafax00 for the responsible disclosure.
Other sources
Socket.IO socket.io-parser is vulnerable to a denial of service, caused by an uncaught exception flaw on the Socket.IO server. By sending a specially crafted Socket.IO packet, a remote attacker could exploit this vulnerability to cause the Node.js process to crash.
— IBM
socket.io parser is a socket.io encoder and decoder written in JavaScript complying with version 5 of socket.io-protocol. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. A patch has been released in version 4.2.3.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2023-32695?
CVE-2023-32695 refers to a vulnerability in the Socket.IO socket.io-parser library that allows for a denial of service attack by triggering an uncaught exception on the server.
What is the severity of CVE-2023-32695?
CVE-2023-32695 has a severity rating of 7.5 (High).
Which software versions are affected by CVE-2023-32695?
Versions between 3.4.0 and 3.4.3 of Socket.io-parser and versions between 4.0.4 and 4.2.3 of Socket.io-parser are affected. Additionally, IBM Watson Knowledge Catalog on-prem 4.x is also affected.
How can I fix CVE-2023-32695?
To fix CVE-2023-32695, update Socket.io-parser to version 4.2.3, which contains a patch for this vulnerability.
Where can I find more information about CVE-2023-32695?
You can find more information about CVE-2023-32695 on the official Socket.IO socket.io-parser GitHub repository and the associated commits.