NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2024-38355: socket.io has an unhandled 'error' event

mediumCVSS 4.0 6.9 · 3.1 7.3GHSA-25hc-qcg6-38wj

Impact A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. Affected versions Version range Needs minor update? ------------------------------------------------------------------ 4.6.2...latest Nothing to do 3.0.0...4.6.1 Please upgrade to [email protected] (at least) 2.3.0...2.5.0 Please upgrade to [email protected] Patches This issue is fixed…

Published Jun 19, 2024 · Updated Sep 24, 2026

Affected packages

socket.io

Ecosystem
npm
Affected
>= 3.0.0, < 4.6.2
Fixed in
4.6.2
Check
npm ls socket.io

socket.io

Ecosystem
npm
Affected
< 2.5.1
Fixed in
2.5.1
Check
npm ls socket.io

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

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
}

Affected versions

| Version range    | Needs minor update?                            |
| `4.6.2...latest` | Nothing to do               |
| `3.0.0...4.6.1`  | Please upgrade to `[email protected]` (at least) |
| `2.3.0...2.5.0`  | Please upgrade to `[email protected]`            |

Patches

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

Workarounds

As a workaround for the affected versions of the socket.io package, you can attach a listener for the "error" event:

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

For more information

If you have any questions or comments about this advisory:

  • Open a discussion here

Thanks a lot to Paul Taylor for the responsible disclosure.

References

  • https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115
  • https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c

Credited to Y0ursTruly, nikpivkin.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology