Skip to content

[GHSA-25hc-qcg6-38wj] socket.io has an unhandled 'error' event #9629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nikpivkin wants to merge 1 commit into
base: nikpivkin/advisory-improvement-9629
Choose a base branch
from
Open

[GHSA-25hc-qcg6-38wj] socket.io has an unhandled 'error' event #9629

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions advisories/github-reviewed/2024/06/GHSA-25hc-qcg6-38wj/GHSA-25hc-qcg6-38wj.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,6 @@
"summary": "socket.io has an unhandled 'error' event",
"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",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L"
},
{
"type": "CVSS_V4",
"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"
Expand All @@ -36,10 +32,7 @@
}
]
}
],
"database_specific": {
"last_known_affected_version_range": "< 2.5.0"
}
]
},
{
"package": {
Expand Down
Loading