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
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/node_modules/ws/package.json
Dependency Hierarchy:
discord.js-12.5.0.tgz (Root Library)
❌ ws-7.4.6.tgz (Vulnerable Library)
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.
Vulnerable Library - discord.js-12.5.0.tgz
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/node_modules/ws/package.json
Vulnerabilities
**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: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/node_modules/ws/package.json
Dependency Hierarchy:
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:
Suggested Fix
Type: Upgrade version
Origin: GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 7.5.10
Direct dependency fix Resolution (discord.js): 12.5.1
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2022-0235
Vulnerable Library - node-fetch-2.6.1.tgz
A light-weight module that brings window.fetch to node.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/ghpr_no_hash_pinning/node_modules/node-fetch/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Publish Date: 2022-01-16
URL: CVE-2022-0235
CVSS 3 Score Details (6.1)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-r683-j2x4-v87g
Release Date: 2022-01-16
Fix Resolution (node-fetch): 2.6.7
Direct dependency fix Resolution (discord.js): 12.5.1
⛑️ 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: