npm CLI vulnerabilities

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>". The password value is not redacted and is printed to stdout and also to any generated log files.

The npm CLI versions prior to 6.13.4 are vulnerable to Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries from being overwritten by other package installations, even with the --ignore-scripts option.

Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. Through the bin field in package.json, a package publisher can access folders outside the intended node_modules directory and modify arbitrary files on a user's system during installation. This vulnerability bypasses the --ignore-scripts install option.

npm CLI versions prior to 6.13.3 are vulnerable to Arbitrary File Write. Packages can create symlinks to files outside node_modules via the bin field in package.json during installation, bypassing the --ignore-scripts option.

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests. This allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

A vulnerability in npm cli allows local attackers to escalate privileges due to incorrect permission assignment when loading modules from an unsecured location. This can lead to arbitrary code execution in the context of a target user.