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.
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/parse-url/package.json
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Vulnerabilities
*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
CVE-2022-37601
### Vulnerable Library - loader-utils-1.4.0.tgzutils 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/loader-utils/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - html-webpack-plugin-4.5.2.tgz - :x: **loader-utils-1.4.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsPrototype 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 FixType: Upgrade version
Release Date: 2022-10-12
Fix Resolution (loader-utils): 1.4.1
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-2216
### Vulnerable Library - parse-url-5.0.2.tgzAn 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: /apps/package.json
Path to vulnerable library: /apps/node_modules/parse-url/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - telemetry-1.3.3.tgz - git-url-parse-11.4.4.tgz - git-up-4.0.2.tgz - :x: **parse-url-5.0.2.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsServer-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 FixType: Upgrade version
Origin: https://huntr.dev/bounties/505a3d39-2723-4a06-b1f7-9b2d133c92e1/
Release Date: 2022-06-27
Fix Resolution (parse-url): 6.0.3
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-37598
### Vulnerable Library - uglify-js-3.13.1.tgzJavaScript parser, mangler/compressor and beautifier toolkit
Library home page: https://registry.npmjs.org/uglify-js/-/uglify-js-3.13.1.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/uglify-js/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - generator-2.15.3.tgz - html-minifier-4.0.0.tgz - :x: **uglify-js-3.13.1.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### 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 FixType: Upgrade version
Release Date: 2022-10-20
Fix Resolution (uglify-js): 3.13.10
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-44906
### Vulnerable Library - minimist-1.2.5.tgzparse 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: - nuxt-2.15.3.tgz (Root Library) - cli-2.15.3.tgz - :x: **minimist-1.2.5.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsMinimist <=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 FixType: Upgrade version
Release Date: 2022-03-17
Fix Resolution (minimist): 1.2.6
Direct dependency fix Resolution (nuxt): 3.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.tgzquote 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: - nuxt-2.15.3.tgz (Root Library) - server-2.15.3.tgz - launch-editor-middleware-2.2.1.tgz - launch-editor-2.2.1.tgz - :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-2900
### Vulnerable Library - parse-url-5.0.2.tgzAn 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: /apps/package.json
Path to vulnerable library: /apps/node_modules/parse-url/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - telemetry-1.3.3.tgz - git-url-parse-11.4.4.tgz - git-up-4.0.2.tgz - :x: **parse-url-5.0.2.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsServer-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 FixType: Upgrade version
Release Date: 2022-09-14
Fix Resolution (parse-url): 8.0.0
Direct dependency fix Resolution (nuxt): 2.15.4
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/loader-utils/node_modules/json5/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - html-webpack-plugin-4.5.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: - nuxt-2.15.3.tgz (Root Library) - babel-preset-app-2.15.3.tgz - core-7.13.10.tgz - :x: **json5-2.2.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsJSON5 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 FixType: 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.4
Fix Resolution (json5): 2.2.2
Direct dependency fix Resolution (nuxt): 2.15.4
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.tgztar 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: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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 (nuxt): 2.15.4
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.tgztar 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: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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 (nuxt): 2.15.4
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.tgztar 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: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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 (nuxt): 2.15.4
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.tgztar 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: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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 (nuxt): 2.15.4
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.tgztar 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: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - cacache-15.0.5.tgz - :x: **tar-6.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe 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 FixType: 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 (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-23424
### Vulnerable Library - ansi-html-0.0.7.tgzAn elegant lib that converts the chalked (ANSI) text to HTML.
Library home page: https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/ansi-html/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - webpack-hot-middleware-2.25.0.tgz - :x: **ansi-html-0.0.7.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThis affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.
Publish Date: 2021-08-18
URL: CVE-2021-23424
### 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 FixType: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-23424
Release Date: 2021-08-18
Fix Resolution (ansi-html): 0.0.8
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-25858
### Vulnerable Libraries - terser-5.6.0.tgz, terser-4.8.0.tgz### terser-5.6.0.tgz
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-5.6.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/terser-webpack-plugin/node_modules/terser/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - terser-webpack-plugin-4.2.3.tgz - :x: **terser-5.6.0.tgz** (Vulnerable Library) ### terser-4.8.0.tgz
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-4.8.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/terser/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - html-webpack-plugin-4.5.2.tgz - html-minifier-terser-5.1.1.tgz - :x: **terser-4.8.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThe package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
Publish Date: 2022-07-15
URL: CVE-2022-25858
### 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 FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25858
Release Date: 2022-07-15
Fix Resolution (terser): 5.14.2
Direct dependency fix Resolution (nuxt): 2.15.4
Fix Resolution (terser): 4.8.1
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2020-28469
### Vulnerable Library - glob-parent-3.1.0.tgzStrips glob magic from a string to provide the parent directory path
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - webpack-4.46.0.tgz - watchpack-1.7.5.tgz - watchpack-chokidar2-2.0.1.tgz - chokidar-2.1.8.tgz - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsThis affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
Publish Date: 2021-06-03
URL: CVE-2020-28469
### 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 FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469
Release Date: 2021-06-03
Fix Resolution (glob-parent): 5.1.2
Direct dependency fix Resolution (nuxt): 3.0.0
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-37620
### Vulnerable Library - html-minifier-4.0.0.tgzHighly configurable, well-tested, JavaScript-based HTML minifier.
Library home page: https://registry.npmjs.org/html-minifier/-/html-minifier-4.0.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/html-minifier/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - generator-2.15.3.tgz - :x: **html-minifier-4.0.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsA Regular Expression Denial of Service (ReDoS) flaw was found in kangax html-minifier 4.0.0 via the candidate variable in htmlminifier.js.
Publish Date: 2022-10-31
URL: CVE-2022-37620
### 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. Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-27290
### Vulnerable Library - ssri-6.0.1.tgzStandard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.
Library home page: https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/webpack/node_modules/ssri/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - webpack-4.46.0.tgz - terser-webpack-plugin-1.4.5.tgz - cacache-12.0.4.tgz - :x: **ssri-6.0.1.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability Detailsssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
Publish Date: 2021-03-12
URL: CVE-2021-27290
### 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 FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-vx3p-948g-6vhq
Release Date: 2021-03-12
Fix Resolution (ssri): 6.0.2
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-38900
### Vulnerable Library - decode-uri-component-0.2.0.tgzA better decodeURIComponent
Library home page: https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/decode-uri-component/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - webpack-4.46.0.tgz - micromatch-3.1.10.tgz - snapdragon-0.8.2.tgz - source-map-resolve-0.5.3.tgz - :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability Detailsdecode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
Publish Date: 2022-11-28
URL: CVE-2022-38900
### 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 FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-w573-4hg7-7wgq
Release Date: 2022-11-28
Fix Resolution (decode-uri-component): 0.2.1
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2021-29059
### Vulnerable Library - is-svg-3.0.0.tgzCheck if a string or buffer is SVG
Library home page: https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz
Path to dependency file: /apps/package.json
Path to vulnerable library: /apps/node_modules/is-svg/package.json
Dependency Hierarchy: - nuxt-2.15.3.tgz (Root Library) - webpack-2.15.3.tgz - cssnano-4.1.10.tgz - cssnano-preset-default-4.0.7.tgz - postcss-svgo-4.0.2.tgz - :x: **is-svg-3.0.0.tgz** (Vulnerable Library)
Found in HEAD commit: 2af7d7cc32e2b991a85a8942ac1b8c1cf7ecd47b
Found in base branch: develop
### Vulnerability DetailsA vulnerability was discovered in IS-SVG version 2.1.0 to 4.2.2 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
Publish Date: 2021-06-21
URL: CVE-2021-29059
### 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 FixType: Upgrade version
Release Date: 2021-06-21
Fix Resolution (is-svg): 4.3.0
Direct dependency fix Resolution (nuxt): 2.15.4
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)