CVE-2024-38355

Unhandled 'error' event in socket.io

Description

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 `socket.io@4.6.2` (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.

Category

7.3
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.10%
Affected: socketio socket.io
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2024-38355?
CVE-2024-38355 has been scored as a high severity vulnerability.
How to fix CVE-2024-38355?
To fix CVE-2024-38355, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-38355 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-38355 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-38355?
CVE-2024-38355 affects socketio socket.io.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.