ghsa-q9mw-68c2-j6m5
Vulnerability from github
Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
TypeError: Cannot read properties of undefined (reading 'handlesUpgrades')
at Server.onWebSocket (build/server.js:515:67)
This impacts all the users of the engine.io
package, including those who uses depending packages like socket.io
.
Patches
A fix has been released today (2023/05/02): 6.4.2
This bug was introduced in version 5.1.0 and included in version 4.1.0 of the socket.io
parent package. Older versions are not impacted.
For socket.io
users:
| Version range | engine.io
version | Needs minor update? |
|-----------------------------|---------------------|--------------------------------------------------------------------------------------------------------|
| socket.io@4.6.x
| ~6.4.0
| npm audit fix
should be sufficient |
| socket.io@4.5.x
| ~6.2.0
| Please upgrade to socket.io@4.6.x
|
| socket.io@4.4.x
| ~6.1.0
| Please upgrade to socket.io@4.6.x
|
| socket.io@4.3.x
| ~6.0.0
| Please upgrade to socket.io@4.6.x
|
| socket.io@4.2.x
| ~5.2.0
| Please upgrade to socket.io@4.6.x
|
| socket.io@4.1.x
| ~5.1.1
| Please upgrade to socket.io@4.6.x
|
| socket.io@4.0.x
| ~5.0.0
| Not impacted |
| socket.io@3.1.x
| ~4.1.0
| Not impacted |
| socket.io@3.0.x
| ~4.0.0
| Not impacted |
| socket.io@2.5.0
| ~3.6.0
| Not impacted |
| socket.io@2.4.x
and below | ~3.5.0
| Not impacted |
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
- Open an issue in
engine.io
Thanks to Thomas Rinsma from Codean for the responsible disclosure.
{ "affected": [ { "package": { "ecosystem": "npm", "name": "engine.io" }, "ranges": [ { "events": [ { "introduced": "5.1.0" }, { "fixed": "6.4.2" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2023-31125" ], "database_specific": { "cwe_ids": [ "CWE-248" ], "github_reviewed": true, "github_reviewed_at": "2023-05-03T21:56:51Z", "nvd_published_at": "2023-05-08T21:15:11Z", "severity": "MODERATE" }, "details": "### Impact\n\nA specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.\n\n```\nTypeError: Cannot read properties of undefined (reading \u0027handlesUpgrades\u0027)\n at Server.onWebSocket (build/server.js:515:67)\n```\n\nThis impacts all the users of the [`engine.io`](https://www.npmjs.com/package/engine.io) package, including those who uses depending packages like [`socket.io`](https://www.npmjs.com/package/socket.io).\n\n### Patches\n\nA fix has been released today (2023/05/02): [6.4.2](https://github.com/socketio/engine.io/releases/tag/6.4.2)\n\nThis bug was introduced in version 5.1.0 and included in version 4.1.0 of the `socket.io` parent package. Older versions are not impacted.\n\nFor `socket.io` users:\n\n| Version range | `engine.io` version | Needs minor update? |\n|-----------------------------|---------------------|--------------------------------------------------------------------------------------------------------|\n| `socket.io@4.6.x` | `~6.4.0` | `npm audit fix` should be sufficient |\n| `socket.io@4.5.x` | `~6.2.0` | Please upgrade to `socket.io@4.6.x` |\n| `socket.io@4.4.x` | `~6.1.0` | Please upgrade to `socket.io@4.6.x` |\n| `socket.io@4.3.x` | `~6.0.0` | Please upgrade to `socket.io@4.6.x` |\n| `socket.io@4.2.x` | `~5.2.0` | Please upgrade to `socket.io@4.6.x` |\n| `socket.io@4.1.x` | `~5.1.1` | Please upgrade to `socket.io@4.6.x` |\n| `socket.io@4.0.x` | `~5.0.0` | Not impacted |\n| `socket.io@3.1.x` | `~4.1.0` | Not impacted |\n| `socket.io@3.0.x` | `~4.0.0` | Not impacted |\n| `socket.io@2.5.0` | `~3.6.0` | Not impacted |\n| `socket.io@2.4.x` and below | `~3.5.0` | Not impacted |\n\n### Workarounds\n\nThere is no known workaround except upgrading to a safe version.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`engine.io`](https://github.com/socketio/engine.io)\n\nThanks to Thomas Rinsma from Codean for the responsible disclosure.\n", "id": "GHSA-q9mw-68c2-j6m5", "modified": "2023-05-09T16:32:21Z", "published": "2023-05-03T21:56:51Z", "references": [ { "type": "WEB", "url": "https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-31125" }, { "type": "WEB", "url": "https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44" }, { "type": "PACKAGE", "url": "https://github.com/socketio/engine.io" }, { "type": "WEB", "url": "https://github.com/socketio/engine.io/releases/tag/6.4.2" }, { "type": "WEB", "url": "https://security.netapp.com/advisory/ntap-20230622-0002" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ], "summary": "engine.io Uncaught Exception vulnerability" }
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.