search

hackariens / react

Templates pour la création d'un nouveau projet react
0 stars 0 forks source link

react-scripts-4.0.3.tgz: 52 vulnerabilities (highest severity is: 9.8) - autoclosed #140

Closed mend-bolt-for-github[bot] closed 1 year ago

mend-bolt-for-github[bot] commented 1 year ago
Vulnerable Library - react-scripts-4.0.3.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/webpack/node_modules/ssri/package.json

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (react-scripts version) Remediation Available
CVE-2021-44906 High 9.8 minimist-1.2.5.tgz Transitive 5.0.1 ❌
CVE-2021-3757 High 9.8 immer-8.0.1.tgz Transitive 5.0.0 ❌
CVE-2022-29078 High 9.8 ejs-2.7.4.tgz Transitive 5.0.1 ❌
CVE-2021-3918 High 9.8 json-schema-0.2.3.tgz Transitive 5.0.0 ❌
CVE-2022-0691 High 9.8 url-parse-1.5.1.tgz Transitive 5.0.0 ❌
CVE-2022-37601 High 9.8 detected in multiple dependencies Transitive 5.0.0 ❌
WS-2021-0153 High 9.8 ejs-2.7.4.tgz Transitive 5.0.0 ❌
CVE-2021-23436 High 9.8 immer-8.0.1.tgz Transitive 5.0.0 ❌
CVE-2021-42740 High 9.8 shell-quote-1.7.2.tgz Transitive 5.0.0 ❌
CVE-2022-1650 High 9.3 eventsource-1.0.7.tgz Transitive 5.0.0 ❌
CVE-2022-0686 High 9.1 url-parse-1.5.1.tgz Transitive 5.0.0 ❌
CVE-2022-46175 High 8.8 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2021-37701 High 8.6 tar-6.1.0.tgz Transitive 5.0.0 ❌
CVE-2021-37712 High 8.6 tar-6.1.0.tgz Transitive 5.0.0 ❌
CVE-2021-37713 High 8.6 tar-6.1.0.tgz Transitive 5.0.0 ❌
CVE-2021-32804 High 8.1 tar-6.1.0.tgz Transitive 5.0.0 ❌
CVE-2021-32803 High 8.1 tar-6.1.0.tgz Transitive 5.0.0 ❌
CVE-2021-43138 High 7.8 async-2.6.3.tgz Transitive 5.0.0 ❌
CVE-2021-27290 High 7.5 ssri-6.0.1.tgz Transitive 5.0.0 ❌
CVE-2021-23382 High 7.5 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2022-37603 High 7.5 detected in multiple dependencies Transitive 5.0.1 ❌
CVE-2021-23343 High 7.5 path-parse-1.0.6.tgz Transitive 5.0.0 ❌
CVE-2021-23424 High 7.5 ansi-html-0.0.7.tgz Transitive 5.0.0 ❌
CVE-2022-25858 High 7.5 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2020-28469 High 7.5 detected in multiple dependencies Transitive 5.0.0 ❌
WS-2021-0152 High 7.5 color-string-1.5.4.tgz Transitive 5.0.0 ❌
CVE-2022-24772 High 7.5 node-forge-0.10.0.tgz Transitive 5.0.0 ❌
CVE-2021-29059 High 7.5 is-svg-3.0.0.tgz Transitive 5.0.0 ❌
CVE-2022-24771 High 7.5 node-forge-0.10.0.tgz Transitive 5.0.0 ❌
CVE-2021-3803 High 7.5 nth-check-1.0.2.tgz Transitive 5.0.1 ❌
CVE-2021-3807 High 7.5 ansi-regex-4.1.0.tgz Transitive 5.0.0 ❌
CVE-2022-24999 High 7.5 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2022-3517 High 7.5 minimatch-3.0.4.tgz Transitive N/A* ❌
CVE-2022-37599 High 7.5 loader-utils-2.0.0.tgz Transitive 5.0.1 ❌
CVE-2021-28092 High 7.5 is-svg-3.0.0.tgz Transitive 5.0.0 ❌
CVE-2021-3777 High 7.5 tmpl-1.0.4.tgz Transitive 5.0.0 ❌
WS-2022-0008 Medium 6.6 node-forge-0.10.0.tgz Transitive 5.0.0 ❌
CVE-2022-0155 Medium 6.5 follow-redirects-1.13.2.tgz Transitive 5.0.0 ❌
CVE-2021-23386 Medium 6.5 dns-packet-1.3.1.tgz Transitive 5.0.0 ❌
CVE-2022-0122 Medium 6.1 node-forge-0.10.0.tgz Transitive 5.0.0 ❌
CVE-2022-0536 Medium 5.9 follow-redirects-1.13.2.tgz Transitive 5.0.0 ❌
CVE-2021-24033 Medium 5.6 react-dev-utils-11.0.3.tgz Transitive 5.0.0 ❌
CVE-2021-23566 Medium 5.5 nanoid-3.1.20.tgz Transitive 5.0.0 ❌
CVE-2022-0512 Medium 5.3 url-parse-1.5.1.tgz Transitive 5.0.0 ❌
CVE-2021-32640 Medium 5.3 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2021-3664 Medium 5.3 url-parse-1.5.1.tgz Transitive 5.0.0 ❌
CVE-2022-24773 Medium 5.3 node-forge-0.10.0.tgz Transitive 5.0.0 ❌
CVE-2021-29060 Medium 5.3 color-string-1.5.4.tgz Transitive 5.0.0 ❌
CVE-2022-0639 Medium 5.3 url-parse-1.5.1.tgz Transitive 5.0.0 ❌
CVE-2021-23362 Medium 5.3 hosted-git-info-2.8.8.tgz Transitive 5.0.0 ❌
CVE-2021-23364 Medium 5.3 detected in multiple dependencies Transitive 5.0.0 ❌
CVE-2021-23368 Medium 5.3 detected in multiple dependencies Transitive 5.0.0 ❌

*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

Partial details (17 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.

CVE-2021-44906 ### Vulnerable Library - minimist-1.2.5.tgz

parse argument options

Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/minimist/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - eslint-plugin-import-2.22.1.tgz - tsconfig-paths-3.9.0.tgz - :x: **minimist-1.2.5.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

Publish Date: 2022-03-17

URL: CVE-2021-44906

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2022-03-17

Fix Resolution (minimist): 1.2.6

Direct dependency fix Resolution (react-scripts): 5.0.1

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-3757 ### Vulnerable Library - immer-8.0.1.tgz

Create your next immutable state by mutating the current one

Library home page: https://registry.npmjs.org/immer/-/immer-8.0.1.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/immer/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - react-dev-utils-11.0.3.tgz - :x: **immer-8.0.1.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

immer is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Publish Date: 2021-09-02

URL: CVE-2021-3757

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://huntr.dev/bounties/23d38099-71cd-42ed-a77a-71e68094adfa/

Release Date: 2021-09-02

Fix Resolution (immer): 9.0.6

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-29078 ### Vulnerable Library - ejs-2.7.4.tgz

Embedded JavaScript templates

Library home page: https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/ejs/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - workbox-webpack-plugin-5.1.4.tgz - workbox-build-5.1.4.tgz - rollup-plugin-off-main-thread-1.4.2.tgz - :x: **ejs-2.7.4.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).

Publish Date: 2022-04-25

URL: CVE-2022-29078

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~

Release Date: 2022-04-25

Fix Resolution (ejs): 3.1.7

Direct dependency fix Resolution (react-scripts): 5.0.1

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-3918 ### Vulnerable Library - json-schema-0.2.3.tgz

JSON Schema validation and specifications

Library home page: https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/json-schema/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - jest-26.6.0.tgz - jest-cli-26.6.3.tgz - jest-config-26.6.3.tgz - jest-environment-jsdom-26.6.2.tgz - jsdom-16.4.0.tgz - request-2.88.2.tgz - http-signature-1.2.0.tgz - jsprim-1.4.1.tgz - :x: **json-schema-0.2.3.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Publish Date: 2021-11-13

URL: CVE-2021-3918

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-3918

Release Date: 2021-11-13

Fix Resolution (json-schema): 0.4.0

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-0691 ### Vulnerable Library - url-parse-1.5.1.tgz

Small footprint URL parser that works seamlessly across Node.js and browser environments

Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/url-parse/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - webpack-dev-server-3.11.1.tgz - sockjs-client-1.5.0.tgz - :x: **url-parse-1.5.1.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.

Publish Date: 2022-02-21

URL: CVE-2022-0691

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0691

Release Date: 2022-02-21

Fix Resolution (url-parse): 1.5.9

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-37601 ### Vulnerable Libraries - loader-utils-1.2.3.tgz, loader-utils-1.4.0.tgz

### loader-utils-1.2.3.tgz

utils for webpack loaders

Library home page: https://registry.npmjs.org/loader-utils/-/loader-utils-1.2.3.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/resolve-url-loader/node_modules/loader-utils/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - resolve-url-loader-3.1.2.tgz - :x: **loader-utils-1.2.3.tgz** (Vulnerable Library) ### loader-utils-1.4.0.tgz

utils for webpack loaders

Library home page: https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/webpack/node_modules/loader-utils/package.json,/apps/node_modules/html-webpack-plugin/node_modules/loader-utils/package.json,/apps/node_modules/babel-loader/node_modules/loader-utils/package.json,/apps/node_modules/mini-css-extract-plugin/node_modules/loader-utils/package.json,/apps/node_modules/postcss-loader/node_modules/loader-utils/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - webpack-4.44.2.tgz - :x: **loader-utils-1.4.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils 2.0.0 via the name variable in parseQuery.js.

Publish Date: 2022-10-12

URL: CVE-2022-37601

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2022-10-12

Fix Resolution (loader-utils): 1.4.1

Direct dependency fix Resolution (react-scripts): 5.0.0

Fix Resolution (loader-utils): 1.4.1

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
WS-2021-0153 ### Vulnerable Library - ejs-2.7.4.tgz

Embedded JavaScript templates

Library home page: https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/ejs/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - workbox-webpack-plugin-5.1.4.tgz - workbox-build-5.1.4.tgz - rollup-plugin-off-main-thread-1.4.2.tgz - :x: **ejs-2.7.4.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Arbitrary Code Injection vulnerability was found in ejs before 3.1.6. Caused by filename which isn't sanitized for display.

Publish Date: 2021-01-22

URL: WS-2021-0153

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2021-01-22

Fix Resolution (ejs): 3.1.6

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-23436 ### Vulnerable Library - immer-8.0.1.tgz

Create your next immutable state by mutating the current one

Library home page: https://registry.npmjs.org/immer/-/immer-8.0.1.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/immer/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - react-dev-utils-11.0.3.tgz - :x: **immer-8.0.1.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

This affects the package immer before 9.0.6. A type confusion vulnerability can lead to a bypass of CVE-2020-28477 when the user-provided keys used in the path parameter are arrays. In particular, this bypass is possible because the condition (p === "__proto__" || p === "constructor") in applyPatches_ returns false if p is ['__proto__'] (or ['constructor']). The === operator (strict equality operator) returns false if the operands have different type.

Publish Date: 2021-09-01

URL: CVE-2021-23436

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23436

Release Date: 2021-09-01

Fix Resolution (immer): 9.0.6

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-42740 ### Vulnerable Library - shell-quote-1.7.2.tgz

quote and parse shell commands

Library home page: https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/shell-quote/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - react-dev-utils-11.0.3.tgz - :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.

Publish Date: 2021-10-21

URL: CVE-2021-42740

### 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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740

Release Date: 2021-10-21

Fix Resolution (shell-quote): 1.7.3

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-1650 ### Vulnerable Library - eventsource-1.0.7.tgz

W3C compliant EventSource client for Node.js and browser (polyfill)

Library home page: https://registry.npmjs.org/eventsource/-/eventsource-1.0.7.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/eventsource/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - webpack-dev-server-3.11.1.tgz - sockjs-client-1.5.0.tgz - :x: **eventsource-1.0.7.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository eventsource/eventsource prior to v2.0.2.

Publish Date: 2022-05-12

URL: CVE-2022-1650

### CVSS 3 Score Details (9.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2022-05-12

Fix Resolution (eventsource): 1.1.1

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-0686 ### Vulnerable Library - url-parse-1.5.1.tgz

Small footprint URL parser that works seamlessly across Node.js and browser environments

Library home page: https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/url-parse/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - webpack-dev-server-3.11.1.tgz - sockjs-client-1.5.0.tgz - :x: **url-parse-1.5.1.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.8.

Publish Date: 2022-02-20

URL: CVE-2022-0686

### CVSS 3 Score Details (9.1)

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: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0686

Release Date: 2022-02-20

Fix Resolution (url-parse): 1.5.8

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-46175 ### Vulnerable Libraries - json5-1.0.1.tgz, json5-2.2.0.tgz

### json5-1.0.1.tgz

JSON for humans.

Library home page: https://registry.npmjs.org/json5/-/json5-1.0.1.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tsconfig-paths/node_modules/json5/package.json,/apps/node_modules/mini-css-extract-plugin/node_modules/json5/package.json,/apps/node_modules/postcss-loader/node_modules/json5/package.json,/apps/node_modules/resolve-url-loader/node_modules/json5/package.json,/apps/node_modules/webpack/node_modules/json5/package.json,/apps/node_modules/babel-loader/node_modules/json5/package.json,/apps/node_modules/html-webpack-plugin/node_modules/json5/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - webpack-4.44.2.tgz - loader-utils-1.4.0.tgz - :x: **json5-1.0.1.tgz** (Vulnerable Library) ### json5-2.2.0.tgz

JSON for humans.

Library home page: https://registry.npmjs.org/json5/-/json5-2.2.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/json5/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - core-7.12.3.tgz - :x: **json5-2.2.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including versions 1.0.1 and 2.2.1 does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 versions 1.0.2, 2.2.2, and later.

Publish Date: 2022-12-24

URL: CVE-2022-46175

### CVSS 3 Score Details (8.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2022-46175

Release Date: 2022-12-24

Fix Resolution (json5): 1.0.2

Direct dependency fix Resolution (react-scripts): 5.0.0

Fix Resolution (json5): 2.2.2

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-37701 ### Vulnerable Library - tar-6.1.0.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tar/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.

Publish Date: 2021-08-31

URL: CVE-2021-37701

### CVSS 3 Score Details (8.6)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc

Release Date: 2021-08-31

Fix Resolution (tar): 6.1.7

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-37712 ### Vulnerable Library - tar-6.1.0.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tar/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.

Publish Date: 2021-08-31

URL: CVE-2021-37712

### CVSS 3 Score Details (8.6)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p

Release Date: 2021-08-31

Fix Resolution (tar): 6.1.9

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-37713 ### Vulnerable Library - tar-6.1.0.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tar/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.

Publish Date: 2021-08-31

URL: CVE-2021-37713

### CVSS 3 Score Details (8.6)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh

Release Date: 2021-08-31

Fix Resolution (tar): 6.1.9

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-32804 ### Vulnerable Library - tar-6.1.0.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tar/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.

Publish Date: 2021-08-03

URL: CVE-2021-32804

### CVSS 3 Score Details (8.1)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9

Release Date: 2021-08-03

Fix Resolution (tar): 6.1.1

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-32803 ### Vulnerable Library - tar-6.1.0.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-6.1.0.tgz

Path to dependency file: /apps/package.json

Path to vulnerable library: /apps/node_modules/tar/package.json

Dependency Hierarchy: - react-scripts-4.0.3.tgz (Root Library) - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: 936546e118f7869172c534d1b6de23486e1deae3

Found in base branch: develop

### Vulnerability Details

The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.

Publish Date: 2021-08-03

URL: CVE-2021-32803

### CVSS 3 Score Details (8.1)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw

Release Date: 2021-08-03

Fix Resolution (tar): 6.1.2

Direct dependency fix Resolution (react-scripts): 5.0.0

Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
mend-bolt-for-github[bot] commented 1 year ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.