forked from homedepot/infinite-wish-board
-
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
react-scripts-3.0.1.tgz: 102 vulnerabilities (highest severity is: 9.8) reachable #24
Labels
Mend: dependency security vulnerability
Security vulnerability detected by Mend
Comments
mend-for-github-com
bot
added
the
Mend: dependency security vulnerability
Security vulnerability detected by Mend
label
Aug 30, 2023
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 78 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 80 vulnerabilities (highest severity is: 9.8)
Nov 15, 2023
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 80 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 81 vulnerabilities (highest severity is: 9.8)
Dec 5, 2023
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 81 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 83 vulnerabilities (highest severity is: 9.8)
Feb 29, 2024
1 task
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 83 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 84 vulnerabilities (highest severity is: 9.8)
Mar 3, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 84 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 90 vulnerabilities (highest severity is: 9.8)
Mar 3, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 90 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 89 vulnerabilities (highest severity is: 9.8)
Mar 23, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 89 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 90 vulnerabilities (highest severity is: 9.8)
Apr 8, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 90 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 91 vulnerabilities (highest severity is: 9.8)
Apr 9, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 91 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 92 vulnerabilities (highest severity is: 9.8)
Apr 17, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 92 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 93 vulnerabilities (highest severity is: 9.8)
Apr 19, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 93 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 94 vulnerabilities (highest severity is: 9.8)
Apr 25, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 94 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 96 vulnerabilities (highest severity is: 9.8)
May 15, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 96 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 97 vulnerabilities (highest severity is: 9.8)
Jun 2, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 97 vulnerabilities (highest severity is: 9.8)
react-scripts-3.0.1.tgz: 97 vulnerabilities (highest severity is: 9.8) reachable
Jun 3, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 97 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 98 vulnerabilities (highest severity is: 9.8) reachable
Jun 19, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 98 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 99 vulnerabilities (highest severity is: 9.8) reachable
Jul 1, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 99 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 100 vulnerabilities (highest severity is: 9.8) reachable
Jul 3, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 100 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 99 vulnerabilities (highest severity is: 9.8) reachable
Jul 18, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 99 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 98 vulnerabilities (highest severity is: 9.8) reachable
Aug 4, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 98 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 102 vulnerabilities (highest severity is: 9.8) reachable
Aug 4, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 102 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 103 vulnerabilities (highest severity is: 9.8) reachable
Aug 28, 2024
mend-for-github-com
bot
changed the title
react-scripts-3.0.1.tgz: 103 vulnerabilities (highest severity is: 9.8) reachable
react-scripts-3.0.1.tgz: 102 vulnerabilities (highest severity is: 9.8) reachable
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Mend: dependency security vulnerability
Security vulnerability detected by Mend
0 participants
Vulnerable Library - react-scripts-3.0.1.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/immer/package.json
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Vulnerabilities
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
*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-2022-24999
Vulnerable Libraries - qs-6.7.0.tgz, qs-6.5.2.tgz
qs-6.7.0.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.7.0.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/express/node_modules/qs/package.json,/ui/node_modules/body-parser/node_modules/qs/package.json
Dependency Hierarchy:
qs-6.5.2.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.5.2.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/qs/package.json,/api/node_modules/qs/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[proto]=b&a[proto]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
Publish Date: 2022-11-26
URL: CVE-2022-24999
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 1.9%
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-24999
Release Date: 2022-11-26
Fix Resolution (qs): 6.7.3
Direct dependency fix Resolution (react-scripts): 3.1.0
Fix Resolution (qs): 6.7.3
Direct dependency fix Resolution (react-scripts): 3.1.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2023-26159
Vulnerable Library - follow-redirects-1.5.10.tgz
HTTP and HTTPS modules that follow redirects.
Library home page: https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.10.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/follow-redirects/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.
Publish Date: 2024-01-02
URL: CVE-2023-26159
Threat Assessment
Exploit Maturity: Proof of concept
EPSS: 0.1%
CVSS 3 Score Details (7.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-26159
Release Date: 2024-01-02
Fix Resolution (follow-redirects): 1.15.4
Direct dependency fix Resolution (react-scripts): 3.1.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-28849
Vulnerable Library - follow-redirects-1.5.10.tgz
HTTP and HTTPS modules that follow redirects.
Library home page: https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.10.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/follow-redirects/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
follow-redirects is an open source, drop-in replacement for Node's
http
andhttps
modules that automatically follows redirects. In affected versions follow-redirects only clears authorization header during cross-domain redirect, but keep the proxy-authentication header which contains credentials too. This vulnerability may lead to credentials leak, but has been addressed in version 1.15.6. Users are advised to upgrade. There are no known workarounds for this vulnerability.Publish Date: 2024-03-14
URL: CVE-2024-28849
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-cxjh-pqwp-8mfp
Release Date: 2024-03-14
Fix Resolution: follow-redirects - 1.15.6
CVE-2022-0155
Vulnerable Library - follow-redirects-1.5.10.tgz
HTTP and HTTPS modules that follow redirects.
Library home page: https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.10.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/follow-redirects/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor
Publish Date: 2022-01-10
URL: CVE-2022-0155
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.2%
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/
Release Date: 2022-01-10
Fix Resolution (follow-redirects): 1.14.7
Direct dependency fix Resolution (react-scripts): 3.1.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-29041
Vulnerable Library - express-4.17.1.tgz
Fast, unopinionated, minimalist web framework
Library home page: https://registry.npmjs.org/express/-/express-4.17.1.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/express/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
Express.js minimalist web framework for node. Versions of Express.js prior to 4.19.0 and all pre-release alpha and beta versions of 5.0 are affected by an open redirect vulnerability using malformed URLs. When a user of Express performs a redirect using a user-provided URL Express performs an encode using
encodeurl
on the contents before passing it to thelocation
header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list. The main method impacted isres.location()
but this is also called from withinres.redirect()
. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.Publish Date: 2024-03-25
URL: CVE-2024-29041
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (6.1)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-rv95-896h-c2vc
Release Date: 2024-03-25
Fix Resolution: express - 4.19.0
CVE-2022-0536
Vulnerable Library - follow-redirects-1.5.10.tgz
HTTP and HTTPS modules that follow redirects.
Library home page: https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.10.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/node_modules/follow-redirects/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
Improper Removal of Sensitive Information Before Storage or Transfer in NPM follow-redirects prior to 1.14.8.
Publish Date: 2022-02-09
URL: CVE-2022-0536
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.1%
CVSS 3 Score Details (2.6)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0536
Release Date: 2022-02-09
Fix Resolution (follow-redirects): 1.14.8
Direct dependency fix Resolution (react-scripts): 3.1.0
⛑️ Automatic Remediation will be attempted for this issue.
MSC-2023-16609
Vulnerable Library - fsevents-1.2.9.tgz
Native Access to Mac OS-X FSEvents
Library home page: https://registry.npmjs.org/fsevents/-/fsevents-1.2.9.tgz
Path to dependency file: /ui/package.json
Path to vulnerable library: /ui/package.json
Dependency Hierarchy:
Found in HEAD commit: c86ac37edecda28046d3157739e16c0e14c30fce
Found in base branch: master
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
This package has been identified by Mend as containing potential malicious functionality. The severity of the functionality can change depending on where the library is running (user's machine or backend server). The following risks were identified: Malware dropper – this package contains a Trojan horse, allowing the unauthorized installation of other potentially malicious software.
Publish Date: 2023-09-20
URL: MSC-2023-16609
Threat Assessment
Exploit Maturity: High
EPSS:
CVSS 3 Score Details (9.8)
Base Score Metrics:
⛑️Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: