*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
npm pack ignores root-level .gitignore and .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=`). Anyone who has run `npm pack` or `npm publish` inside a workspace, as of v7.9.0 and v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include. Users should upgrade to the latest, patched version of npm v8.11.0, run: npm i -g npm@latest . Node.js versions v16.15.1, v17.19.1, and v18.3.0 include the patched v8.11.0 version of npm.
Vulnerable Library - @verdaccio/e2e-cli-npm6-1.0.1-6-next.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Found in HEAD commit: 6580df98f62d821bca93d2b0acd528447eafe22b
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2022-29244
### Vulnerable Library - npm-6.14.17.tgza package manager for JavaScript
Library home page: https://registry.npmjs.org/npm/-/npm-6.14.17.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy: - @verdaccio/e2e-cli-npm6-1.0.1-6-next.5.tgz (Root Library) - :x: **npm-6.14.17.tgz** (Vulnerable Library)
Found in HEAD commit: 6580df98f62d821bca93d2b0acd528447eafe22b
Found in base branch: master
### Vulnerability Detailsnpm pack ignores root-level .gitignore and .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=`). Anyone who has run `npm pack` or `npm publish` inside a workspace, as of v7.9.0 and v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include. Users should upgrade to the latest, patched version of npm v8.11.0, run: npm i -g npm@latest . Node.js versions v16.15.1, v17.19.1, and v18.3.0 include the patched v8.11.0 version of npm.
### CVSS 3 Score Details (7.5)Publish Date: 2022-06-13
URL: CVE-2022-29244
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: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-hj9c-8jmm-8c52
Release Date: 2022-06-13
Fix Resolution: npm - 8.11.0