Symlink Following Affecting npm10 package, versions <10.18.0-1.15.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.18% (57th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES150-NPM10-2719495
  • published14 Apr 2022
  • disclosed15 Jan 2020

Introduced: 15 Jan 2020

CVE-2019-16775  (opens in a new tab)
CWE-61  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 npm10 to version 10.18.0-1.15.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream npm10 package and not the npm10 package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

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.

CVSS Scores

version 3.1