{"answers":{"affected":"2 open source packages ship an affected version, including engine.io. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-31125 in the wild and no public exploit code.","fix":"Upgrade engine.io to 6.4.2 or later.","what":"CVE-2023-31125 is a medium-severity denial of service vulnerability in socketio engine.io, published on 8 May 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31125 and fix it if it is affected.\n\nWhat it is: CVE-2023-31125 is a medium-severity denial of service vulnerability in socketio engine.io, published on 8 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-31125 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- engine.io (npm): affected from 5.1.0; fixed in 6.4.2\n- engine.io (npm): affected from 5.1.0; fixed in 6.4.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-31125/ (Markdown: https://insights.sbomify.com/CVE-2023-31125/index.md)","id":"CVE-2023-31125","markdown":"https://insights.sbomify.com/CVE-2023-31125/index.md","name":"CVE-2023-31125","record":{"aliases":["GHSA-q9mw-68c2-j6m5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js communication library","requires_auth":"low_privilege","summary":"A specially crafted HTTP request triggers an uncaught exception in Engine.IO, crashing the Node.js process and causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"engine.io","vendor":"socket"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Uncaught exception in engine.io","id":"CVE-2023-31125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":2,"n_references":4,"next":{"headline":"Improper Neutralization of Invalid Characters in Data Attribute Names in org.xwiki.commons:xwiki-commons-xml","id":"CVE-2023-31126"},"packages":[{"ecosystem":"npm","fixed":["6.4.2"],"introduced":["5.1.0"],"last_affected":[],"package":"engine.io","purl":null,"source":"GHSA-q9mw-68c2-j6m5"},{"ecosystem":"npm","fixed":["6.4.2"],"introduced":["5.1.0"],"last_affected":[],"package":"engine.io","purl":"pkg:npm/engine.io","source":"GHSA-q9mw-68c2-j6m5"}],"prev":{"headline":"AutoTools does not set CARES_RANDOM_FILE during cross compilation","id":"CVE-2023-31124"},"products":["engine.io"],"published":"2023-05-08","related":[{"cvss_score":7.5,"headline":"Socket.IO: Engine.IO WebTransport SID DoS","id":"CVE-2026-59724","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":7.5,"headline":"Socket.IO: Engine.IO Polling Transport Connection Exhaustion","id":"CVE-2026-59725","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":7.5,"headline":"Uncaught Exception in engine.io","id":"CVE-2022-21676","kev_date_added":null,"published":"2022-01-12"},{"cvss_score":7.5,"headline":"Resource exhaustion in engine.io","id":"CVE-2020-36048","kev_date_added":null,"published":"2021-01-07"},{"cvss_score":7.1,"headline":"Uncaught exception in engine.io","id":"CVE-2022-41940","kev_date_added":null,"published":"2022-11-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["socketio"]},"summary":"A specially crafted HTTP request triggers an uncaught exception in Engine.IO, crashing the Node.js process and causing denial of service.","url":"https://insights.sbomify.com/CVE-2023-31125/"}