Vulnerable Library - nuxt-2.15.4.tgz
A minimalistic framework for server-rendered Vue.js applications (inspired by Next.js)
Library home page: https://registry.npmjs.org/nuxt/-/nuxt-2.15.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/nuxt/package.json
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Vulnerabilities
| CVE |
Severity |
 CVSS |
Dependency |
Type |
Fixed in (nuxt version) |
Remediation Possible** |
| CVE-2023-42282 |
 Critical |
9.8 |
ip-1.1.5.tgz |
Transitive |
2.15.5 |
β |
| CVE-2023-3224 |
Critical |
9.8 |
nuxt-2.15.4.tgz |
Direct |
2.17.1 |
β |
| CVE-2022-37601 |
Critical |
9.8 |
loader-utils-1.4.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-37598 |
Critical |
9.8 |
uglify-js-3.13.3.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-2216 |
Critical |
9.8 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-44906 |
Critical |
9.8 |
minimist-1.2.5.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-42740 |
Critical |
9.8 |
shell-quote-1.7.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-2900 |
Critical |
9.1 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2023-45133 |
 High |
8.8 |
traverse-7.13.13.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-46175 |
High |
8.8 |
detected in multiple dependencies |
Transitive |
2.15.5 |
β |
| CVE-2021-37713 |
High |
8.6 |
tar-6.1.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-37712 |
High |
8.6 |
tar-6.1.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-37701 |
High |
8.6 |
tar-6.1.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-32804 |
High |
8.1 |
tar-6.1.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-32803 |
High |
8.1 |
tar-6.1.0.tgz |
Transitive |
2.15.5 |
β |
| WS-2022-0238 |
High |
7.5 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| WS-2022-0237 |
High |
7.5 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2023-46234 |
High |
7.5 |
browserify-sign-4.2.1.tgz |
Transitive |
N/A* |
β |
| CVE-2022-38900 |
High |
7.5 |
decode-uri-component-0.2.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-37620 |
High |
7.5 |
html-minifier-4.0.0.tgz |
Transitive |
N/A* |
β |
| CVE-2022-37603 |
High |
7.5 |
loader-utils-1.4.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-25883 |
High |
7.5 |
detected in multiple dependencies |
Transitive |
N/A* |
β |
| CVE-2022-25858 |
High |
7.5 |
detected in multiple dependencies |
Transitive |
2.15.5 |
β |
| CVE-2022-24999 |
High |
7.5 |
qs-6.10.1.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-0722 |
High |
7.5 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-3807 |
High |
7.5 |
detected in multiple dependencies |
Transitive |
2.15.5 |
β |
| CVE-2021-3803 |
High |
7.5 |
detected in multiple dependencies |
Transitive |
2.16.0 |
β |
| CVE-2021-29059 |
High |
7.5 |
is-svg-3.0.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-28092 |
High |
7.5 |
is-svg-3.0.0.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-27290 |
High |
7.5 |
ssri-6.0.1.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23424 |
High |
7.5 |
ansi-html-0.0.7.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23382 |
High |
7.5 |
postcss-7.0.35.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23343 |
High |
7.5 |
path-parse-1.0.6.tgz |
Transitive |
2.15.5 |
β |
| CVE-2020-28469 |
High |
7.5 |
glob-parent-3.1.0.tgz |
Transitive |
3.0.0 |
β |
| CVE-2024-29180 |
High |
7.4 |
webpack-dev-middleware-4.1.0.tgz |
Transitive |
2.16.0 |
β |
| CVE-2022-0624 |
High |
7.3 |
parse-path-4.0.3.tgz |
Transitive |
2.15.5 |
β |
| WS-2023-0301 |
High |
7.1 |
nuxt-2.15.4.tgz |
Direct |
2.17.2 |
β |
| CVE-2024-28863 |
 Medium |
6.5 |
tar-6.1.0.tgz |
Transitive |
N/A* |
β |
| WS-2022-0239 |
Medium |
6.1 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-3224 |
Medium |
6.1 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-2218 |
Medium |
6.1 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-2217 |
Medium |
6.1 |
parse-url-5.0.2.tgz |
Transitive |
2.15.5 |
β |
| CVE-2022-0235 |
Medium |
6.1 |
node-fetch-2.6.1.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23566 |
Medium |
5.5 |
nanoid-3.1.22.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-32640 |
Medium |
5.3 |
ws-7.4.4.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23368 |
Medium |
5.3 |
postcss-7.0.35.tgz |
Transitive |
2.15.5 |
β |
| CVE-2021-23364 |
Medium |
5.3 |
browserslist-4.16.3.tgz |
Transitive |
2.15.5 |
β |
*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
Partial details (18 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-2023-42282
Vulnerable Library - ip-1.1.5.tgz
[](https://www.npmjs.com/package/ip)
Library home page: https://registry.npmjs.org/ip/-/ip-1.1.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ip/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- server-2.15.4.tgz
- β ip-1.1.5.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
The ip package before 1.1.9 for Node.js might allow SSRF because some IP addresses (such as 0x7f.1) are improperly categorized as globally routable via isPublic.
Publish Date: 2024-02-08
URL: CVE-2023-42282
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: GHSA-78xj-cgh5-2h22
Release Date: 2024-02-08
Fix Resolution (ip): 1.1.9
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2023-3224
Vulnerable Library - nuxt-2.15.4.tgz
A minimalistic framework for server-rendered Vue.js applications (inspired by Next.js)
Library home page: https://registry.npmjs.org/nuxt/-/nuxt-2.15.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/nuxt/package.json
Dependency Hierarchy:
- β nuxt-2.15.4.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
Code Injection in GitHub repository nuxt/nuxt prior to 3.5.3.
Publish Date: 2023-06-13
URL: CVE-2023-3224
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/1eb74fd8-0258-4c1f-a904-83b52e373a87/
Release Date: 2023-06-13
Fix Resolution: 2.17.1
Step up your Open Source Security Game with Mend here
CVE-2022-37601
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: /package.json
Path to vulnerable library: /node_modules/vue-style-loader/node_modules/loader-utils/package.json,/node_modules/loader-utils/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- vue-style-loader-4.1.3.tgz
- β loader-utils-1.4.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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
Origin: GHSA-76p3-8jx3-jpfq
Release Date: 2022-10-12
Fix Resolution (loader-utils): 1.4.1
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2022-37598
Vulnerable Library - uglify-js-3.13.3.tgz
JavaScript parser, mangler/compressor and beautifier toolkit
Library home page: https://registry.npmjs.org/uglify-js/-/uglify-js-3.13.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/uglify-js/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- generator-2.15.4.tgz
- html-minifier-4.0.0.tgz
- β uglify-js-3.13.3.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
** DISPUTED ** Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.
Publish Date: 2022-10-20
URL: CVE-2022-37598
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-20
Fix Resolution (uglify-js): 3.13.10
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2022-2216
Vulnerable Library - parse-url-5.0.2.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- telemetry-1.3.3.tgz
- git-url-parse-11.4.4.tgz
- git-up-4.0.2.tgz
- β parse-url-5.0.2.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 7.0.0.
Publish Date: 2022-06-27
URL: CVE-2022-2216
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/505a3d39-2723-4a06-b1f7-9b2d133c92e1/
Release Date: 2022-06-27
Fix Resolution (parse-url): 6.0.1
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/minimist/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- html-webpack-plugin-4.5.2.tgz
- loader-utils-1.4.0.tgz
- json5-1.0.1.tgz
- β minimist-1.2.5.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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
Origin: GHSA-xvch-5gv4-984h
Release Date: 2022-03-17
Fix Resolution (minimist): 1.2.6
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/shell-quote/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- server-2.15.4.tgz
- launch-editor-middleware-2.2.1.tgz
- launch-editor-2.2.1.tgz
- β shell-quote-1.7.2.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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 (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2022-2900
Vulnerable Library - parse-url-5.0.2.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- telemetry-1.3.3.tgz
- git-url-parse-11.4.4.tgz
- git-up-4.0.2.tgz
- β parse-url-5.0.2.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0.
Publish Date: 2022-09-14
URL: CVE-2022-2900
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
Release Date: 2022-09-14
Fix Resolution (parse-url): 8.0.0
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2023-45133
Vulnerable Library - traverse-7.13.13.tgz
The Babel Traverse module maintains the overall tree state, and is responsible for replacing, removing, and adding nodes
Library home page: https://registry.npmjs.org/@babel/traverse/-/traverse-7.13.13.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@babel/traverse/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- babel-preset-app-2.15.4.tgz
- core-7.13.14.tgz
- β traverse-7.13.13.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
Babel is a compiler for writingJavaScript. In @babel/traverse prior to versions 7.23.2 and 8.0.0-alpha.4 and all versions of babel-traverse, using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the path.evaluate()or path.evaluateTruthy() internal Babel methods. Known affected plugins are @babel/plugin-transform-runtime; @babel/preset-env when using its useBuiltIns option; and any "polyfill provider" plugin that depends on @babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regenerator. No other plugins under the @babel/ namespace are impacted, but third-party plugins might be. Users that only compile trusted code are not impacted. The vulnerability has been fixed in @babel/[email protected] and @babel/[email protected]. Those who cannot upgrade @babel/traverse and are using one of the affected packages mentioned above should upgrade them to their latest version to avoid triggering the vulnerable code path in affected @babel/traverse versions: @babel/plugin-transform-runtime v7.23.2, @babel/preset-env v7.23.2, @babel/helper-define-polyfill-provider v0.4.3, babel-plugin-polyfill-corejs2 v0.4.6, babel-plugin-polyfill-corejs3 v0.8.5, babel-plugin-polyfill-es-shims v0.10.0, babel-plugin-polyfill-regenerator v0.5.3.
Publish Date: 2023-10-12
URL: CVE-2023-45133
CVSS 3 Score Details (8.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- 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: GHSA-67hx-6x53-jw92
Release Date: 2023-10-12
Fix Resolution (@babel/traverse): 7.23.2
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/json5/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- html-webpack-plugin-4.5.2.tgz
- loader-utils-1.4.0.tgz
- β 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: /package.json
Path to vulnerable library: /node_modules/json5/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- babel-preset-app-2.15.4.tgz
- core-7.13.14.tgz
- β json5-2.2.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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 (nuxt): 2.15.5
Fix Resolution (json5): 1.0.2
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- terser-webpack-plugin-4.2.3.tgz
- cacache-15.0.6.tgz
- β tar-6.1.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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: GHSA-5955-9wpr-37jh
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.9
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- terser-webpack-plugin-4.2.3.tgz
- cacache-15.0.6.tgz
- β tar-6.1.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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: GHSA-qq89-hq3f-393p
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.9
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- terser-webpack-plugin-4.2.3.tgz
- cacache-15.0.6.tgz
- β tar-6.1.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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: GHSA-9r2w-394v-53qc
Release Date: 2021-08-31
Fix Resolution (tar): 6.1.7
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- terser-webpack-plugin-4.2.3.tgz
- cacache-15.0.6.tgz
- β tar-6.1.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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: GHSA-3jfq-g458-7qm9
Release Date: 2021-08-03
Fix Resolution (tar): 6.1.1
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
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: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- terser-webpack-plugin-4.2.3.tgz
- cacache-15.0.6.tgz
- β tar-6.1.0.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
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: GHSA-r628-mhmh-qjhw
Release Date: 2021-08-03
Fix Resolution (tar): 6.1.2
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
WS-2022-0238
Vulnerable Library - parse-url-5.0.2.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- telemetry-1.3.3.tgz
- git-url-parse-11.4.4.tgz
- git-up-4.0.2.tgz
- β parse-url-5.0.2.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
File Protocol Spoofing in parse-url before 8.0.0 can lead to attacks, such as XSS, Arbitrary Read/Write File, and Remote Code Execution.
Publish Date: 2022-06-30
URL: WS-2022-0238
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- 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/52060edb-e426-431b-a0d0-e70407e44f18/
Release Date: 2022-06-30
Fix Resolution (parse-url): 8.0.0
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
WS-2022-0237
Vulnerable Library - parse-url-5.0.2.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- telemetry-1.3.3.tgz
- git-url-parse-11.4.4.tgz
- git-up-4.0.2.tgz
- β parse-url-5.0.2.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
Regular Expression Denial of Service (ReDoS) in ionicabizau/parse-url before 8.0.0.
It allows cause a denial of service when calling function parse-url
Publish Date: 2022-07-04
URL: WS-2022-0237
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
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2022-07-04
Fix Resolution (parse-url): 8.0.0
Direct dependency fix Resolution (nuxt): 2.15.5
Step up your Open Source Security Game with Mend here
CVE-2023-46234
Vulnerable Library - browserify-sign-4.2.1.tgz
adds node crypto signing for browsers
Library home page: https://registry.npmjs.org/browserify-sign/-/browserify-sign-4.2.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/browserify-sign/package.json
Dependency Hierarchy:
- nuxt-2.15.4.tgz (Root Library)
- webpack-2.15.4.tgz
- webpack-4.46.0.tgz
- node-libs-browser-2.2.1.tgz
- crypto-browserify-3.12.0.tgz
- β browserify-sign-4.2.1.tgz (Vulnerable Library)
Found in HEAD commit: d15d896364c4214a7c2d8c1b52008e06cea6bc1e
Found in base branch: master
Vulnerability Details
browserify-sign is a package to duplicate the functionality of node's crypto public key functions, much of this is based on Fedor Indutny's work on indutny/tls.js. An upper bound check issue in dsaVerify function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. This issue has been patched in version 4.2.2.
Publish Date: 2023-10-26
URL: CVE-2023-46234
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: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-x9w5-v3q2-3rhw
Release Date: 2023-10-26
Fix Resolution: browserify-sign - 4.2.2
Step up your Open Source Security Game with Mend here
![mend-bolt-for-github[bot] avatar](https://avatars.githubusercontent.com/in/16809?v=4 "mend-bolt-for-github[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent