GitHub Advisoryadvisory · npm

GHSA-hj9c-8jmm-8c52 Packing does not respect root-level ignore files in workspaces

HIGH Published 2022-06-02 Modified 2022-06-29 Official page ↗
Aliases
CVE-2022-29244
Ecosystem
npm
Packages
npm
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-200
Reviewed
2022-06-02

Affected packages

• npm npm: >= 7.9.0, < 8.11.0 → fixed in 8.11.0

Description

Impact `npm pack` ignores root-level `.gitignore` & `.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` with workspaces, as of v7.9.0 & v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include. Patch • Upgrade to the latest, patched version of `npm` (`v8.11.0` or greater), run: `npm i -g npm@latest` • Node.js versions `v16.15.1`, `v17.19.1` & `v18.3.0` include the patched `v8.11.0` version of `npm` Steps to take to see if you're impacted 1. Run `npm publish --dry-run` or `npm pack` with an `npm` version `>=7.9.0` & `` (ex. `npm pack --workspace=foo`) 2. Check the output in your terminal which will list the package contents (note: `tar -tvf ` also works) 3. If you find that there are files included you did not expect, you should: 3.1. Create & publish a new release excluding those files (ref. "Keeping files out of your Package") 3.2. Deprecate the old package (ex. `npm deprecate [@] `) 3.3. Revoke or rotate any sensitive information (ex. passwords, tokens, secrets etc.) which might have been exposed References • CVE-2022-29244 • `npm-packlist` • `libnpmpack` • `libnpmpublish`

Related

Alias · CVE (1)

  • CVE-2022-29244 npm pack ignores root-level .gitignore and .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. vulnerability

Weakness · CWE (1)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness

References