npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option. ## Recommendation Upgrade to version 6.13.4 or later.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-16777US | medium6.5 | — | ||
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package i… | ||||
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-4328-8hgf-7wjrADVISORY
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