CVE-2023-31125
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of service disruption.
- Exploit odds
- 1.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.3% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.3% · EPSS, next 30 days
- Weakness
- CWE-248
- Record status
- Modified
Affected
- Socket engine.io < 6.4.2
Attack profile CVSS 3.1 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-31125.md and follow it. Check whether this project is affected by CVE-2023-31125. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44
- https://github.com/socketio/engine.io/releases/tag/6.4.2
- https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5
- https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44
- https://github.com/socketio/engine.io/releases/tag/6.4.2
- https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5
References
- https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44
- https://github.com/socketio/engine.io/releases/tag/6.4.2
- https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5
- https://security.netapp.com/advisory/ntap-20230622-0002/
- https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44
- https://github.com/socketio/engine.io/releases/tag/6.4.2
- https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5
- https://security.netapp.com/advisory/ntap-20230622-0002/