Bug 2203761 (CVE-2023-31125) - CVE-2023-31125 engine.io: Uncaught exception in engine.io
Summary: CVE-2023-31125 engine.io: Uncaught exception in engine.io
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2023-31125
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2203762
Blocks: 2196617
TreeView+ depends on / blocked
 
Reported: 2023-05-15 08:04 UTC by Avinash Hanwate
Modified: 2023-05-16 13:16 UTC (History)
3 users (show)

Fixed In Version: engine.io 6.4.2
Clone Of:
Environment:
Last Closed: 2023-05-16 13:16:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2023-05-15 08:04:33 UTC
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.


https://github.com/socketio/engine.io/releases/tag/6.4.2
https://github.com/socketio/engine.io/commit/fc480b4f305e16fe5972cf337d055e598372dc44
https://github.com/socketio/engine.io/security/advisories/GHSA-q9mw-68c2-j6m5

Comment 1 Avinash Hanwate 2023-05-15 08:04:49 UTC
Created magicmirror tracking bugs for this issue:

Affects: fedora-all [bug 2203762]

Comment 2 Product Security DevOps Team 2023-05-16 13:16:41 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2023-31125


Note You need to log in before you can comment on or make changes to this bug.