You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit 15af22fc22 which has been included in socket.io@4.6.2 (released in May 2023). The fix was backported in the 2.x branch as well with commit d30630ba10. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.
CVE-2024-38355 - High Severity Vulnerability
Vulnerable Library - socket.io-3.1.2.tgz
node.js realtime framework server
Library home page: https://registry.npmjs.org/socket.io/-/socket.io-3.1.2.tgz
Path to dependency file: /frontend/package.json
Path to vulnerable library: /frontend/node_modules/socket.io/package.json,/node_modules/socket.io/package.json
Dependency Hierarchy:
Found in HEAD commit: ba236fd18ec3e6450d68d675bce1609d2e5d3230
Found in base branch: main
Vulnerability Details
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit
15af22fc22
which has been included insocket.io@4.6.2
(released in May 2023). The fix was backported in the 2.x branch as well with commitd30630ba10
. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.Publish Date: 2024-06-19
URL: CVE-2024-38355
CVSS 3 Score Details (7.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-25hc-qcg6-38wj
Release Date: 2024-06-19
Fix Resolution: 4.6.2
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: