search

qcif / data-curator

Data Curator - share usable open data
MIT License
265 stars 38 forks source link

[Security] Bump npm from 6.4.1 to 6.13.6 #976

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps npm from 6.4.1 to 6.13.6. 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.6

6.13.6 (2020-01-09)

DEPENDENCIES

v6.13.5

6.13.5 (2020-01-09)

BUG FIXES

TESTING

DOCUMENTATION

v6.13.4

6.13.4 (2019-12-11)

BUGFIXES

DEPENDENCIES

v6.13.3

6.13.3 (2019-12-09)

DEPENDENCIES

  • 19ce061a2 bin-links@1.1.5 Properly normalize, sanitize, and verify bin entries in package.json.
  • 59c836aae npm-packlist@1.4.7
... (truncated)
Changelog

Sourced from npm's changelog.

6.13.6 (2020-01-09)

DEPENDENCIES

6.13.5 (2020-01-09)

BUG FIXES

TESTING

DOCUMENTATION

6.13.4 (2019-12-11)

BUGFIXES

DEPENDENCIES

... (truncated)
Commits
Maintainer changes

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


Dependabot compatibility score

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) - 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)
dependabot-preview[bot] commented 4 years ago

Superseded by #981.