npm symlink reference outside of node_modules
Versions of the npm CLI prior to 6.13.3 are vulnerable to a symlink reference outside of node_modules. It is possible for packages to create symlinks to files outside of the`node_modules` folder through the `bin` field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user’s system when the package is installed. Only files accessible by the user running the `npm install` are affected. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option. ## Recommendation Upgrade to version 6.13.3 or later.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-16776US | high8.1 | — | ||
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin… | ||||
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00027.htmlWEB
- https://access.redhat.com/errata/RHEA-2020:0330WEB
- https://access.redhat.com/errata/RHSA-2020:0573WEB
- https://access.redhat.com/errata/RHSA-2020:0579WEB
- https://access.redhat.com/errata/RHSA-2020:0597WEB
- https://access.redhat.com/errata/RHSA-2020:0602WEB
- https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cliWEB
- https://github.com/advisories/GHSA-x8qc-rrcw-4r46ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan