4 results (0.005 seconds)

CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0

CVE-2022-29244 – npm packing does not respect root-level ignore files in workspaces

https://notcve.org/view.php?id=CVE-2022-29244

13 Jun 2022 — 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 v1... • https://github.com/nodejs/node/pull/43210 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer •

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 3

CVE-2021-43616 – npm: npm ci succeeds when package-lock.json doesn't match package.json

https://notcve.org/view.php?id=CVE-2021-43616

13 Nov 2021 — The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependenc... • https://github.com/icatalina/CVE-2021-43616 • CWE-345: Insufficient Verification of Data Authenticity •

CVSS: 8.2EPSS: 0%CPEs: 5EXPL: 0

CVE-2021-39135 – UNIX Symbolic Link (Symlink) Following in @npmcli/arborist

https://notcve.org/view.php?id=CVE-2021-39135

31 Aug 2021 — `@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, ... • https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf • CWE-59: Improper Link Resolution Before File Access ('Link Following') CWE-61: UNIX Symbolic Link (Symlink) Following •

CVSS: 8.2EPSS: 1%CPEs: 5EXPL: 0

CVE-2021-39134 – UNIX Symbolic Link (Symlink) Following in @npmcli/arborist

https://notcve.org/view.php?id=CVE-2021-39134

31 Aug 2021 — `@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multi... • https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf • CWE-61: UNIX Symbolic Link (Symlink) Following CWE-178: Improper Handling of Case Sensitivity •