Arbitrary File Write in npm
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 field. A properly constructed entry in the package.json bin field would allow a package publisher to create files on a user's system when the package is installed. It is only possible to affect files that the user running `npm install` has access to and it is not possible to over write files that already exist on disk. 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-16775US | medium6.5 | — | ||
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through… | ||||
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-m6cx-g6qm-p2cxADVISORY
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