chore(deps): [security] bump npm from 6.11.3 to 6.13.7

[dependabot-preview[bot]]

Bumps npm from 6.11.3 to 6.13.7. This update includes security fixes.

Vulnerabilities fixed

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.13.7

6.13.7 (2020-01-28)

BUG FIXES

• 7dbb91438 #655 Update CI detection cases (@isaacs)

DEPENDENCIES

• 0fb1296c7 libnpx@10.2.2 (@mikemimik)
• c9b69d569 node-gyp@5.0.7 (@mikemimik)
• e8dbaf452 bin-links@1.1.7 (@mikemimik)
  • #613 Fixes bin entry for package

v6.13.6

6.13.6 (2020-01-09)

DEPENDENCIES

• 6dba897a1 pacote@9.5.12:
  • d2f4176 fix(git): Do not drop uid/gid when executing in root-owned directory (@isaacs)

v6.13.5

6.13.5 (2020-01-09)

BUG FIXES

• fd0a802ec #550 Fix cache location for npm ci (@zhenyavinogradov)
• 4b30f3cca #648 fix(version): using 'allow-same-version', git commit --allow-empty and git tag -f (@rhengles)

TESTING

• e16f68d30 test(ci): add failing cache config test (@ruyadorno)
• 3f009fbf2 #659 test: fix bin-overwriting test on Windows (@isaacs)
• 43ae0791f #601 ci: Allow builds to run even if one fails (@XhmikosR)
• 4a669bee4 #603 Remove the unused appveyor.yml (@XhmikosR)
• 9295046ac #600 ci: switch to actions/checkout@v2 (@XhmikosR)

DOCUMENTATION

• f2d770ac7 #569 fix netlify publish path config (@claudiahdz)
• 462cf0983 #627 update gatsby dependencies (@felixonmars)
• 6fb5dbb72 #532 docs: clarify usage of global prefix (@jgehrcke)

v6.13.4

6.13.4 (2019-12-11)

BUGFIXES

• 320ac9aee npm/bin-links#12 npm/gentle-fs#7 Do not remove global bin/man links inappropriately (@isaacs)

... (truncated)

Changelog

Sourced from npm's changelog.

6.13.7 (2020-01-28)

BUG FIXES

• 7dbb91438 #655 Update CI detection cases (@isaacs)

DEPENDENCIES

• 0fb1296c7 libnpx@10.2.2 (@mikemimik)
• c9b69d569 node-gyp@5.0.7 (@mikemimik)
• e8dbaf452 bin-links@1.1.7 (@mikemimik)
  • #613 Fixes bin entry for package

6.13.6 (2020-01-09)

DEPENDENCIES

• 6dba897a1 pacote@9.5.12:
  • d2f4176 fix(git): Do not drop uid/gid when executing in root-owned directory (@isaacs)

6.13.5 (2020-01-09)

BUG FIXES

• fd0a802ec #550 Fix cache location for npm ci (@zhenyavinogradov)
• 4b30f3cca #648 fix(version): using 'allow-same-version', git commit --allow-empty and git tag -f (@rhengles)

TESTING

• e16f68d30 test(ci): add failing cache config test (@ruyadorno)
• 3f009fbf2 #659 test: fix bin-overwriting test on Windows (@isaacs)
• 43ae0791f #601 ci: Allow builds to run even if one fails (@XhmikosR)
• 4a669bee4 #603 Remove the unused appveyor.yml (@XhmikosR)
• 9295046ac #600 ci: switch to actions/checkout@v2 (@XhmikosR)

DOCUMENTATION

• f2d770ac7 #569 fix netlify publish path config (@claudiahdz)
• 462cf0983 #627 update gatsby dependencies (@felixonmars)
• 6fb5dbb72

... (truncated)

Commits

• f533d61 6.13.7
• 5897df4 update AUTHORS
• dcafdd9 updated changelog for npm@6.13.7
• 0fb1296 libnpx@10.2.2
• 1a5d209 chore: removed reference to package.community as a source for npm team support
• 68fc88e docs: updated the CONTRIBUTING file; added references to benchmarking
• 1ce0344 feat: updated workflow for pull-ruquest benchmark dispatch requests
• 5967fa4 feat: added workflow file for commenting on a pull-request to dispatch trigge...
• 3590e40 fix: removed authorization header from benchmark dispatch request
• c9b69d5 node-gyp@5.0.7
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by mikemimik, 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](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #121.