Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Uncaught exception in engine.io

CVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 CVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 6.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by engine.io 6.4.2KEV status unknown

cve-program · CVE-2023-31125

Published

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Read the publisher's advisory

euvd · EUVD-2023-1610

Published

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Read the publisher's advisory

nvd · CVE-2023-31125

Published

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Read the publisher's advisory

osv · GHSA-q9mw-68c2-j6m5

Published

### 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`](https://www.npmjs.com/package/engine.io) package, including those who uses depending packages like [`socket.io`](https://www.npmjs.com/package/socket.io). ### Patches A fix has been released today (2023/05/02): [6.4.2](https://github.com/socketio/engine.io/releases/tag/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? | |-----------------------------|---------------------|--------------------------------------------------------------------------------------------------------| | `[email protected]` | `~6.4.0` | `npm audit fix` should be sufficient | | `[email protected]` | `~6.2.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~6.1.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~6.0.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.2.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.1.1` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.0.0` | Not impacted | | `[email protected]` | `~4.1.0` | Not impacted | | `[email protected]` | `~4.0.0` | Not impacted | | `[email protected]` | `~3.6.0` | Not impacted | | `[email protected]` 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`](https://github.com/socketio/engine.io) Thanks to Thomas Rinsma from Codean for the responsible disclosure.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2023-31125

Published

Uncaught exception in engine.io

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Source published
8 May 2023 20:21:01 UTC
Source modified
13 Feb 2025 16:49:44 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2023-1610

Published

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability was introduced in version 5.1.0 and included in version 4.1.0 of the `socket…

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 8, 2023, 8:21:01 PM

dateUpdated: Feb 13, 2025, 4:49:44 PM

2 related source bulletins · separate from aliases

WID-SEC-W-2026-0180: Dell Data Protection Advisor: Mehrere Schwachstellen

CVE-2009-2625 · CVE-2010-4252 · CVE-2010-5298 · CVE-2011-1473 · CVE-2011-1945 · CVE-2012-0027 · CVE-2012-0213 · CVE-2012-0881 · CVE-2012-6153 · CVE-2013-0166 · CVE-2013-0169 · CVE-2013-4002 · CVE-2013-4366 · CVE-2013-7285 · CVE-2014-0076 · CVE-2014-0114 · CVE-2014-0195 · CVE-2014-0221 · CVE-2014-0224 · CVE-2014-3470 · CVE-2014-3488 · CVE-2014-3490 · CVE-2014-3505 · CVE-2014-3506 · CVE-2014-3507 · CVE-2014-3510 · CVE-2014-3529 · CVE-2014-3558 · CVE-2014-3566 · CVE-2014-3567 · CVE-2014-3568 · CVE-2014-3570 · CVE-2014-3571 · CVE-2014-3572 · CVE-2014-3574 · CVE-2014-3623 · CVE-2014-7839 · CVE-2014-8122 · CVE-2014-8125 · CVE-2014-8176 · CVE-2014-8275 · CVE-2014-9527 · CVE-2015-0204 · CVE-2015-0209 · CVE-2015-0286 · CVE-2015-0287 · CVE-2015-0288 · CVE-2015-0289 · CVE-2015-0292 · CVE-2015-0293 · CVE-2015-1788 · CVE-2015-1789 · CVE-2015-1790 · CVE-2015-1791 · CVE-2015-1792 · CVE-2015-2156 · CVE-2015-3158 · CVE-2015-3195 · CVE-2015-4000 · CVE-2015-5241 · CVE-2015-5253 · CVE-2016-0703 · CVE-2016-0704 · CVE-2016-0750 · CVE-2016-2105 · CVE-2016-2106 · CVE-2016-2107 · CVE-2016-2108 · CVE-2016-2109 · CVE-2016-2141 · CVE-2016-2176 · CVE-2016-2177 · CVE-2016-2178 · CVE-2016-2179 · CVE-2016-2180 · CVE-2016-2181 · CVE-2016-2182 · CVE-2016-2183 · CVE-2016-2510 · CVE-2016-3674 · CVE-2016-4606 · CVE-2016-4802 · CVE-2016-5000 · CVE-2016-5419 · CVE-2016-5420 · CVE-2016-5421 · CVE-2016-6302 · CVE-2016-6303 · CVE-2016-6304 · CVE-2016-6345 · CVE-2016-6346 · CVE-2016-6347 · CVE-2016-6348 · CVE-2016-6812 · CVE-2016-7056 · CVE-2016-7141 · CVE-2016-7167 · CVE-2016-8610 · CVE-2016-8615 · CVE-2016-8616 · CVE-2016-8617 · CVE-2016-8618 · CVE-2016-8619 · CVE-2016-8620 · CVE-2016-8621 · CVE-2016-8622 · CVE-2016-8623 · CVE-2016-8624 · CVE-2016-8625 · CVE-2016-8739 · CVE-2016-9586 · CVE-2016-9594 · CVE-2016-9840 · CVE-2016-9841 · CVE-2016-9842 · CVE-2016-9843 · CVE-2016-9878 · CVE-2016-9952 · CVE-2016-9953 · CVE-2017-1000100 · CVE-2017-1000101 · CVE-2017-1000207 · CVE-2017-1000208 · CVE-2017-1000254 · CVE-2017-1000257 · CVE-2017-1000487 · CVE-2017-12626 · CVE-2017-15089 · CVE-2017-15095 · CVE-2017-17485 · CVE-2017-2629 · CVE-2017-2638 · CVE-2017-3156 · CVE-2017-3735 · CVE-2017-3737 · CVE-2017-5644 · CVE-2017-5662 · CVE-2017-5929 · CVE-2017-7525 · CVE-2017-7957 · CVE-2017-8816 · CVE-2017-8817 · CVE-2017-9502 · CVE-2018-1000007 · CVE-2018-1000120 · CVE-2018-1000121 · CVE-2018-1000122 · CVE-2018-1000301 · CVE-2018-1000632 · CVE-2018-1002200 · CVE-2018-10237 · CVE-2018-11307 · CVE-2018-11771 · CVE-2018-12022 · CVE-2018-1275 · CVE-2018-14371 · CVE-2018-14618 · CVE-2018-14718 · CVE-2018-14719 · CVE-2018-14720 · CVE-2018-14721 · CVE-2018-16839 · CVE-2018-16842 · CVE-2018-16890 · CVE-2018-19360 · CVE-2018-19361 · CVE-2018-19362 · CVE-2018-25032 · CVE-2018-8013 · CVE-2018-8039 · CVE-2019-10086 · CVE-2019-10158 · CVE-2019-10173 · CVE-2019-10174 · CVE-2019-10219 · CVE-2019-12086 · CVE-2019-12384 · CVE-2019-12406 · CVE-2019-12415 · CVE-2019-12419 · CVE-2019-12423 · CVE-2019-12814 · CVE-2019-14379 · CVE-2019-14439 · CVE-2019-14540 · CVE-2019-14892 · CVE-2019-14893 · CVE-2019-1559 · CVE-2019-16168 · CVE-2019-16335 · CVE-2019-16942 · CVE-2019-16943 · CVE-2019-17091 · CVE-2019-17267 · CVE-2019-17531 · CVE-2019-17566 · CVE-2019-17573 · CVE-2019-19645 · CVE-2019-19646 · CVE-2019-20330 · CVE-2019-3822 · CVE-2019-3823 · CVE-2019-5427 · CVE-2019-5436 · CVE-2019-5443 · CVE-2019-5482 · CVE-2020-10650 · CVE-2020-10673 · CVE-2020-10969 · CVE-2020-11655 · CVE-2020-11656 · CVE-2020-11979 · CVE-2020-11987 · CVE-2020-13434 · CVE-2020-13435 · CVE-2020-13630 · CVE-2020-13631 · CVE-2020-13632 · CVE-2020-13954 · CVE-2020-14297 · CVE-2020-15250 · CVE-2020-15358 · CVE-2020-1945 · CVE-2020-1954 · CVE-2020-1968 · CVE-2020-24025 · CVE-2020-24616 · CVE-2020-24750 · CVE-2020-25711 · CVE-2020-26217 · CVE-2020-26258 · CVE-2020-26259 · CVE-2020-28499 · CVE-2020-35490 · CVE-2020-35491 · CVE-2020-35728 · CVE-2020-36179 · CVE-2020-36180 · CVE-2020-36181 · CVE-2020-36182 · CVE-2020-36183 · CVE-2020-36184 · CVE-2020-36185 · CVE-2020-36186 · CVE-2020-36187 · CVE-2020-36188 · CVE-2020-36189 · CVE-2020-6950 · CVE-2020-8177 · CVE-2020-8231 · CVE-2020-8284 · CVE-2020-8285 · CVE-2020-8286 · CVE-2020-8840 · CVE-2020-9546 · CVE-2020-9547 · CVE-2020-9548 · CVE-2021-20190 · CVE-2021-20250 · CVE-2021-21341 · CVE-2021-21342 · CVE-2021-21343 · CVE-2021-21344 · CVE-2021-21345 · CVE-2021-21346 · CVE-2021-21347 · CVE-2021-21348 · CVE-2021-21349 · CVE-2021-21350 · CVE-2021-21351 · CVE-2021-21363 · CVE-2021-21364 · CVE-2021-22570 · CVE-2021-22876 · CVE-2021-22898 · CVE-2021-22922 · CVE-2021-22923 · CVE-2021-22924 · CVE-2021-22925 · CVE-2021-22926 · CVE-2021-22946 · CVE-2021-22947 · CVE-2021-23839 · CVE-2021-23840 · CVE-2021-23841 · CVE-2021-23926 · CVE-2021-27568 · CVE-2021-29425 · CVE-2021-29505 · CVE-2021-33813 · CVE-2021-35515 · CVE-2021-35516 · CVE-2021-35517 · CVE-2021-36090 · CVE-2021-36373 · CVE-2021-3712 · CVE-2021-39139 · CVE-2021-39140 · CVE-2021-39141 · CVE-2021-39144 · CVE-2021-39145 · CVE-2021-39146 · CVE-2021-39147 · CVE-2021-39148 · CVE-2021-39149 · CVE-2021-39150 · CVE-2021-39151 · CVE-2021-39152 · CVE-2021-39153 · CVE-2021-39154 · CVE-2021-4044 · CVE-2021-42550 · CVE-2021-43859 · CVE-2022-0084 · CVE-2022-0778 · CVE-2022-22576 · CVE-2022-25758 · CVE-2022-25883 · CVE-2022-25927 · CVE-2022-26336 · CVE-2022-27774 · CVE-2022-27776 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-32206 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-33987 · CVE-2022-3509 · CVE-2022-3510 · CVE-2022-35252 · CVE-2022-35737 · CVE-2022-37434 · CVE-2022-38778 · CVE-2022-38900 · CVE-2022-40151 · CVE-2022-41704 · CVE-2022-41940 · CVE-2022-41966 · CVE-2022-4244 · CVE-2022-4245 · CVE-2022-42890 · CVE-2022-43552 · CVE-2022-44729 · CVE-2022-44730 · CVE-2022-45688 · CVE-2023-0842 · CVE-2023-1370 · CVE-2023-20860 · CVE-2023-26136 · CVE-2023-26159 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27538 · CVE-2023-28319 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-31125 · CVE-2023-32697 · CVE-2023-35116 · CVE-2023-37460 · CVE-2023-38546 · CVE-2023-44270 · CVE-2023-45133 · CVE-2023-45853 · CVE-2023-46218 · CVE-2023-7104 · CVE-2024-22243 · CVE-2024-51127 · CVE-2024-7264 · CVE-2025-31257 · CVE-2025-53057 · CVE-2025-53066 · CVE-2025-61748 · CVE-2025-61755

WID-SEC-W-2023-1800: HCL BigFix: Mehrere Schwachstellen

CVE-2023-32695 · CVE-2023-31125 · CVE-2023-30533 · CVE-2023-28155 · CVE-2023-28023 · CVE-2023-28021 · CVE-2023-28020 · CVE-2023-28019 · CVE-2021-43138

Source published
May 8, 2023, 8:21:01 PM (timezone not stated)
Source modified
Feb 13, 2025, 4:49:44 PM (timezone not stated)
Saved here
16 Nov 2026 03:37:01 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd · CVE-2023-31125

Published

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability was introduced in version 5.1.0 and included in version 4.1.0 of the `socket…

Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. An uncaught exception vulnerability 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. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package, including those who use depending packages like `socket.io`. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-248 · NVD-CWE-Other

Original publisher date fields

published: 2023-05-08T21:15:11.347

lastModified: 2026-06-17T05:56:19.340

1 source CPE criteria · context only
  • cpe:2.3:a:socket:engine.io:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
8 May 2023 21:15:11 UTC
Source modified
17 Jun 2026 05:56:19 UTC
Saved here
24 Oct 2026 22:17:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 · [email protected] · Primary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

osv · GHSA-q9mw-68c2-j6m5

Published

engine.io Uncaught Exception vulnerability

### 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`](https://www.npmjs.com/package/engine.io) package, including those who uses depending packages like [`socket.io`](https://www.npmjs.com/package/socket.io). ### Patches A fix has been released today (2023/05/02): [6.4.2](https://github.com/socketio/engine.io/releases/tag/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? | |-----------------------------|---------------------|--------------------------------------------------------------------------------------------------------| | `[email protected]` | `~6.4.0` | `npm audit fix` should be sufficient | | `[email protected]` | `~6.2.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~6.1.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~6.0.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.2.0` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.1.1` | Please upgrade to `[email protected]` | | `[email protected]` | `~5.0.0` | Not impacted | | `[email protected]` | `~4.1.0` | Not impacted | | `[email protected]` | `~4.0.0` | Not impacted | | `[email protected]` | `~3.6.0` | Not impacted | | `[email protected]` 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`](https://github.com/socketio/engine.io) Thanks to Thomas Rinsma from Codean for the responsible disclosure.

Source published
3 May 2023 21:56:51 UTC
Source modified
10 Sep 2026 03:50:08 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current