CVE-2024-38355

socket.io has an unhandled 'error' event

io.on("connection", (socket) => {
  socket.on("error", () => {
    // ...
  });
});

A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.

node:events:502
    throw err; // Unhandled 'error' event
    ^

Error [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)
    at new NodeError (node:internal/errors:405:5)
    at Socket.emit (node:events:500:17)
    at /myapp/node_modules/socket.io/lib/socket.js:531:14
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
  code: 'ERR_UNHANDLED_ERROR',
  context: undefined
}

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-38355 has a CVSS score of 7.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.1, 4.6.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in [email protected] (released in May 2023).

The fix was backported in the 2.x branch today: https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c

1. What is CVE-2024-38355? CVE-2024-38355 is a medium-severity improper input validation vulnerability in socket.io (npm), affecting versions < 2.5.0. It is fixed in 2.5.1, 4.6.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2024-38355? CVE-2024-38355 has a CVSS score of 7.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of socket.io are affected by CVE-2024-38355? socket.io (npm) versions < 2.5.0 is affected.
4. Is there a fix for CVE-2024-38355? Yes. CVE-2024-38355 is fixed in 2.5.1, 4.6.2. Upgrade to this version or later.
5. Is CVE-2024-38355 exploitable, and should I be worried? Whether CVE-2024-38355 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-38355 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-38355?
   • Upgrade socket.io to 2.5.1 or later
   • Upgrade socket.io to 4.6.2 or later

Other vulnerabilities in socket.io