ghsa-25hc-qcg6-38wj
Vulnerability from github
6.9 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
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 socket.io@4.6.2 (at least) |
| 2.3.0...2.5.0 | Please upgrade to socket.io@2.5.1 |
Patches
This issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in socket.io@4.6.2 (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:
js
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
{ affected: [ { database_specific: { last_known_affected_version_range: "< 2.5.0", }, package: { ecosystem: "npm", name: "socket.io", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "2.5.1", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "npm", name: "socket.io", }, ranges: [ { events: [ { introduced: "3.0.0", }, { fixed: "4.6.2", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2024-38355", ], database_specific: { cwe_ids: [ "CWE-20", "CWE-754", ], github_reviewed: true, github_reviewed_at: "2024-06-19T15:04:41Z", nvd_published_at: "2024-06-19T20:15:11Z", severity: "MODERATE", }, details: "### Impact\n\nA specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.\n\n```\nnode:events:502\n throw err; // Unhandled 'error' event\n ^\n\nError [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)\n at new NodeError (node:internal/errors:405:5)\n at Socket.emit (node:events:500:17)\n at /myapp/node_modules/socket.io/lib/socket.js:531:14\n at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {\n code: 'ERR_UNHANDLED_ERROR',\n context: undefined\n}\n```\n\n### Affected versions\n\n| Version range | Needs minor update? |\n|------------------|------------------------------------------------|\n| `4.6.2...latest` | Nothing to do |\n| `3.0.0...4.6.1` | Please upgrade to `socket.io@4.6.2` (at least) |\n| `2.3.0...2.5.0` | Please upgrade to `socket.io@2.5.1` |\n\n### Patches\n\nThis issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in `socket.io@4.6.2` (released in May 2023).\n\nThe fix was backported in the 2.x branch today: https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c\n\n### Workarounds\n\nAs a workaround for the affected versions of the `socket.io` package, you can attach a listener for the \"error\" event:\n\n```js\nio.on(\"connection\", (socket) => {\n socket.on(\"error\", () => {\n // ...\n });\n});\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open a discussion [here](https://github.com/socketio/socket.io/discussions)\n\nThanks a lot to [Paul Taylor](https://github.com/Y0ursTruly) for the responsible disclosure.\n\n### References\n\n- https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115\n- https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c\n", id: "GHSA-25hc-qcg6-38wj", modified: "2024-11-18T16:26:46Z", published: "2024-06-19T15:04:41Z", references: [ { type: "WEB", url: "https://github.com/socketio/socket.io/security/advisories/GHSA-25hc-qcg6-38wj", }, { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-38355", }, { type: "WEB", url: "https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115", }, { type: "WEB", url: "https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c", }, { type: "PACKAGE", url: "https://github.com/socketio/socket.io", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", type: "CVSS_V3", }, { score: "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N", type: "CVSS_V4", }, ], summary: "socket.io has an unhandled 'error' event", }
Log in or create an account to share your comment.
This schema specifies the format of a comment related to a security advisory.
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.