-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Vulnerable Library - socket.io-4.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ws/package.json
Found in HEAD commit: d2bcda0f0c639b1be7baa4fee5a8a1c0609b45f0
Vulnerabilities
CVE | Severity | Dependency | Type | Fixed in (socket.io version) | Remediation Available | |
---|---|---|---|---|---|---|
CVE-2022-2421 | 9.8 | socket.io-parser-4.0.4.tgz | Transitive | N/A* | ❌ | |
CVE-2022-21676 | 7.5 | engine.io-5.0.0.tgz | Transitive | 4.2.0 | ✅ | |
CVE-2022-41940 | 6.5 | engine.io-5.0.0.tgz | Transitive | N/A* | ❌ | |
CVE-2021-32640 | 5.3 | ws-7.4.4.tgz | Transitive | 4.0.1 | ✅ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.
Details
CVE-2022-2421
Vulnerable Library - socket.io-parser-4.0.4.tgz
socket.io protocol parser
Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-4.0.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/socket.io-parser/package.json
Dependency Hierarchy:
- socket.io-4.0.0.tgz (Root Library)
- ❌ socket.io-parser-4.0.4.tgz (Vulnerable Library)
Found in HEAD commit: d2bcda0f0c639b1be7baa4fee5a8a1c0609b45f0
Found in base branch: main
Vulnerability Details
Due to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.
Publish Date: 2022-10-26
URL: CVE-2022-2421
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://csirt.divd.nl/cases/DIVD-2022-00045/
Release Date: 2022-10-26
Fix Resolution: socket.io-parser - 4.0.5,4.2.1
CVE-2022-21676
Vulnerable Library - engine.io-5.0.0.tgz
The realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
Library home page: https://registry.npmjs.org/engine.io/-/engine.io-5.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/engine.io/package.json
Dependency Hierarchy:
- socket.io-4.0.0.tgz (Root Library)
- ❌ engine.io-5.0.0.tgz (Vulnerable Library)
Found in HEAD commit: d2bcda0f0c639b1be7baa4fee5a8a1c0609b45f0
Found in base branch: main
Vulnerability Details
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. 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 starting from version 4.0.0
, including those who uses depending packages like socket.io
. Versions prior to 4.0.0
are not impacted. A fix has been released for each major branch, namely 4.1.2
for the 4.x.x
branch, 5.2.1
for the 5.x.x
branch, and 6.1.1
for the 6.x.x
branch. There is no known workaround except upgrading to a safe version.
Publish Date: 2022-01-12
URL: CVE-2022-21676
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-273r-mgr4-v34f
Release Date: 2022-01-12
Fix Resolution (engine.io): 5.2.1
Direct dependency fix Resolution (socket.io): 4.2.0
⛑️ Automatic Remediation is available for this issue
CVE-2022-41940
Vulnerable Library - engine.io-5.0.0.tgz
The realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
Library home page: https://registry.npmjs.org/engine.io/-/engine.io-5.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/engine.io/package.json
Dependency Hierarchy:
- socket.io-4.0.0.tgz (Root Library)
- ❌ engine.io-5.0.0.tgz (Vulnerable Library)
Found in HEAD commit: d2bcda0f0c639b1be7baa4fee5a8a1c0609b45f0
Found in base branch: main
Vulnerability Details
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. 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 uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
Publish Date: 2022-11-22
URL: CVE-2022-41940
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-r7qp-cfhv-p84w
Release Date: 2022-11-22
Fix Resolution: engine.io - 3.6.1,6.2.1
CVE-2021-32640
Vulnerable Library - ws-7.4.4.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-7.4.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ws/package.json
Dependency Hierarchy:
- socket.io-4.0.0.tgz (Root Library)
- engine.io-5.0.0.tgz
- ❌ ws-7.4.4.tgz (Vulnerable Library)
- engine.io-5.0.0.tgz
Found in HEAD commit: d2bcda0f0c639b1be7baa4fee5a8a1c0609b45f0
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server library for Node.js. A specially crafted value of the Sec-Websocket-Protocol
header can be used to significantly slow down a ws server. The vulnerability has been fixed in ws@7.4.6 (websockets/ws@00c425e). In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the --max-http-header-size=size
and/or the maxHeaderSize
options.
Publish Date: 2021-05-25
URL: CVE-2021-32640
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: GHSA-6fc8-4gx4-v693
Release Date: 2021-05-25
Fix Resolution (ws): 7.4.6
Direct dependency fix Resolution (socket.io): 4.0.1
⛑️ Automatic Remediation is available for this issue
⛑️ Automatic Remediation is available for this issue.