-
-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Vulnerable Library - log4brains-1.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Vulnerabilities
| CVE | Severity | Dependency | Type | Fixed in (log4brains version) | Remediation Possible** | |
|---|---|---|---|---|---|---|
| CVE-2024-37890 | 7.5 | ws-7.4.6.tgz | Transitive | N/A* | ❌ | |
| CVE-2024-38355 | 7.3 | socket.io-2.5.0.tgz | Transitive | N/A* | ❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-37890
Vulnerable Library - ws-7.4.6.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.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
- log4brains-1.0.1.tgz (Root Library)
- web-1.0.1.tgz
- socket.io-client-2.5.0.tgz
- engine.io-client-3.5.3.tgz
- ❌ ws-7.4.6.tgz (Vulnerable Library)
- engine.io-client-3.5.3.tgz
- socket.io-client-2.5.0.tgz
- web-1.0.1.tgz
Found in base branch: main
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
Publish Date: 2024-06-17
URL: CVE-2024-37890
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-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution: ws - 5.2.4,6.2.3,7.5.10,8.17.1
Step up your Open Source Security Game with Mend here
CVE-2024-38355
Vulnerable Library - socket.io-2.5.0.tgz
node.js realtime framework server
Library home page: https://registry.npmjs.org/socket.io/-/socket.io-2.5.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
- log4brains-1.0.1.tgz (Root Library)
- web-1.0.1.tgz
- ❌ socket.io-2.5.0.tgz (Vulnerable Library)
- web-1.0.1.tgz
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 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.
Publish Date: 2024-06-19
URL: CVE-2024-38355
CVSS 3 Score Details (7.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: GHSA-25hc-qcg6-38wj
Release Date: 2024-06-19
Fix Resolution: socket.io - 2.5.1,4.6.2
Step up your Open Source Security Game with Mend here