-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web3-4.9.0.tgz: 1 vulnerabilities (highest severity is: 8.7) #27
Comments
This issue has been automatically marked as |
This issue has been automatically marked as |
This issue was closed because it has been stalled for 7 days with no activity. |
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory. |
This issue has been automatically marked as |
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/web3-providers-ws/node_modules/ws/package.json
Found in HEAD commit: 141277bbe1dbdc1d667de53b0177a226b25277eb
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - ws-8.17.0.tgz
Library home page: https://registry.npmjs.org/ws/-/ws-8.17.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/web3-providers-ws/node_modules/ws/package.json
Dependency Hierarchy:
Found in HEAD commit: 141277bbe1dbdc1d667de53b0177a226b25277eb
Found in base branch: master
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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 4 Score Details (8.7)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 8.17.1
Direct dependency fix Resolution (web3): 4.10.0
⛑️ Automatic Remediation will be attempted for this issue.
⛑️Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: