[Security] Bump npm from 6.1.0 to 6.14.6

[dependabot-preview]

Bumps npm from 6.1.0 to 6.14.6. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Sensitive information exposure through logs in npm CLI 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 ://[[:]@][:][:][/]. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected versions: < 6.14.6

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects npm

Unauthorized File Access

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 possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Thank you Daniel Ruf for responsibly reporting the issue!

Further information: npm blog post

Affected versions: < 6.13.3

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects npm

Arbitrary File Write

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 modify and/or gain access to arbitrary files on a user’s system when the package is installed.

This behavior is possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Thank you Daniel Ruf for reporting the issue!

Further information: npm blog post

Affected versions: < 6.13.3

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects npm

Arbitrary File Overwrite

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 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 previous serve binary.

This behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Thank you to Daniel Ruf for reporting the issue!

Further information: npm blog post

Affected versions: < 6.13.4

Release notes

Sourced from npm's releases.

v6.14.6

6.14.6 (2020-07-07)

BUG FIXES

• a9857b8f6 chore: remove auth info from logs (@claudiahdz)
• b7ad77598 #1416 fix: wrong npm doctor command result (@vanishcode)

DEPENDENCIES

• 94eca6377 npm-registry-fetch@4.0.5 (@claudiahdz)
• c49b6ae28 #1418 spdx-license-ids@3.0.5 (@kemitchell)

v6.14.5

6.14.5 (2020-05-04)

BUG FIXES

• 33ec41f18 #758 fix: relativize file links when inflating shrinkwrap (@jsnajdr)
• 94ed456df #1162 fix: npm init help output (@mum-never-proud)

DEPENDENCIES

• 5587ac01f npm-registry-fetch@4.0.4
  • fc5d94c39 fix: removed default timeout
• 07a4d8884 graceful-fs@4.2.4
• 8228d1f2e mkdirp@0.5.5
• e6d208317 nopt@4.0.3

v6.14.4

6.14.4 (2020-03-25)

DEPENDENCIES

• 136832dca mkdirp@0.5.4
• Bump minimist@1.2.5 transitive dep to resolve security issue
  • 9c554fd8c update-notifier@2.5.0
  • bump deep-extend@1.2.5
  • bump is-ci@1.2.1
  • bump is-retry-allowed@1.2.0
  • bump rc@1.2.8
  • bump registry-auth-token@3.4.0
  • bump widest-line@2.0.1
• 8bf99b2b5 #1053 deps: updates term-size to use signed binary

v6.14.3

6.14.3 (2020-03-19)

DOCUMENTATION

• 4ad221487 #1020 docs(teams): updated team docs to reflect MFA workflow (@blkdm0n)

Changelog

Sourced from npm's changelog.

6.14.6 (2020-07-07)

BUG FIXES

• a9857b8f6 chore: remove auth info from logs (@claudiahdz)
• b7ad77598 #1416 fix: wrong npm doctor command result (@vanishcode)

DEPENDENCIES

• 94eca6377 npm-registry-fetch@4.0.5 (@claudiahdz)
• c49b6ae28 #1418 spdx-license-ids@3.0.5 (@kemitchell)

DOCUMENTATION

• 2e052984b #1459 chore(docs): fixed links to cli commands (@claudiahdz)
• 0ca3509ca #1283 Update npm-link.md (@peterfich)
• 3dd429e9a #1377 Add note about dropped * filenames (@maxwellgerber)
• 9a2e2e797 #1429 Fix typo (@seanpoulter)

6.14.5 (2020-05-01)

BUG FIXES

• 33ec41f18 #758 fix: relativize file links when inflating shrinkwrap (@jsnajdr)
• 94ed456df #1162 fix: npm init help output (@mum-never-proud)

DEPENDENCIES

• 5587ac01f npm-registry-fetch@4.0.4
  • fc5d94c39 fix: removed default timeout
• 07a4d8884 graceful-fs@4.2.4
• 8228d1f2e mkdirp@0.5.5
• e6d208317 nopt@4.0.3

6.14.4 (2020-03-24)

DEPENDENCIES

• Bump minimist@1.2.5 transitive dep to resolve security issue
  • 9c554fd8c update-notifier@2.5.0
  • bump deep-extend@1.2.5
  • bump deep-extend@0.6.0
  • bump is-ci@1.2.1
  • bump is-retry-allowed@1.2.0
  • bump rc@1.2.8
  • bump registry-auth-token@3.4.0
  • bump widest-line@2.0.1

Commits

• 7352eb6 6.14.6
• f8a3f0e update AUTHORS
• ccaaaab docs: changelog for 6.14.6
• 94eca63 npm-registry-fetch@4.0.5
• a9857b8 chore: remove auth info from logs
• 479e45c style: fix lint error with no trailing comma
• 1aec4cb test: add test for npm doctor that ping registry returns error
• b7ad775 fix: wrong npm doctor command result
• 9a2e2e7 docs: Fix typo
• c49b6ae spdx-license-ids@3.0.5
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by claudiahdz, a new releaser for npm since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)