CVE-2024-38355
Socket.IO is an open source, real-time, bidirectional, event-based, …
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `[email protected]` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115
- github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c
- github.com/socketio/socket.io/security/advisories/GHSA-25hc-qcg6-38wj
- www.vicarius.io/vsociety/posts/unhandled-exception-in-socketio-cve-2024-38355
- nvd.nist.gov/vuln/detail/CVE-2024-38355
- github.com/advisories/GHSA-25hc-qcg6-38wj
- nvd.nist.gov/vuln/detail/CVE-2024-38355
- cve.org/CVERecord?id=CVE-2024-38355
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.