CVE-2019-16775: UNIX Symbolic Link (Symlink) Following
(updated )
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 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. This behavior is still possible through install scripts. This vulnerability bypasses a user using the –ignore-scripts install option.
References
- lists.opensuse.org/opensuse-security-announce/2020-01/msg00027.html
- access.redhat.com/errata/RHEA-2020:0330
- access.redhat.com/errata/RHSA-2020:0573
- access.redhat.com/errata/RHSA-2020:0579
- access.redhat.com/errata/RHSA-2020:0597
- access.redhat.com/errata/RHSA-2020:0602
- blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli
- github.com/advisories/GHSA-m6cx-g6qm-p2cx
- github.com/npm/cli/security/advisories/GHSA-m6cx-g6qm-p2cx
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z36UKPO5F3PQ3Q2POMF5LEKXWAH5RUFP/
- nvd.nist.gov/vuln/detail/CVE-2019-16775
- www.npmjs.com/advisories/1434
- www.oracle.com/security-alerts/cpujan2020.html
- www.oracle.com/security-alerts/cpuoct2021.html
Code Behaviors & Features
Detect and mitigate CVE-2019-16775 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →