discord-ghost
discord-ghost copied to clipboard
build(deps): [Security] Bump npm from 6.10.1 to 6.14.7
Bumps npm from 6.10.1 to 6.14.7. 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 the
node_modules
folder through thebin
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 thebin
field. A properly constructed entry in the package.jsonbin
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 aserve
binary would overwrite the previousserve
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.7
BUG FIXES
de5108836
#784 npm explore spawn shell correctly (@jasisk)36e6c01d3
git tag handling regression on shrinkwrap (@claudiahdz)1961c9369
#288 Fix package id in shrinkwrap lifecycle step output (@bz2)87888892a
#1009 gracefully handle error during npm install (@danielleadams)6fe2bdc25
#1547 npm ls --parseable --long output (@ruyadorno)DEPENDENCIES
2d78481c7
update mkdirp on tacks (@claudiahdz)4e129d105
uninstall npm-registry-couchapp (@claudiahdz)8e1869e27
update marked dev dep (@claudiahdz)6a6151f37
[email protected]
(@claudiahdz)dc21422eb
[email protected]
(@claudiahdz)d341f88ce
[email protected]
(@claudiahdz)3e168d49b
[email protected]
(@claudiahdz)6ae942a51
[email protected]
(@claudiahdz)6a35e3dee
[email protected]
(@claudiahdz)v6.14.6
6.14.6 (2020-07-07)
BUG FIXES
a9857b8f6
chore: remove auth info from logs (@claudiahdz)b7ad77598
#1416 fix: wrongnpm doctor
command result (@vanishcode)DEPENDENCIES
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
[email protected]
fc5d94c39
fix: removed default timeout07a4d8884
[email protected]
8228d1f2e
[email protected]
e6d208317
[email protected]
v6.14.4
6.14.4 (2020-03-25)
DEPENDENCIES
Changelog
Sourced from npm's changelog.
6.14.7 (2020-07-21)
BUG FIXES
de5108836
#784 npm explore spawn shell correctly (@jasisk)36e6c01d3
git tag handling regression on shrinkwrap (@claudiahdz)1961c9369
#288 Fix package id in shrinkwrap lifecycle step output (@bz2)87888892a
#1009 gracefully handle error during npm install (@danielleadams)6fe2bdc25
#1547 npm ls --parseable --long output (@ruyadorno)DEPENDENCIES
2d78481c7
update mkdirp on tacks (@claudiahdz)4e129d105
uninstall npm-registry-couchapp (@claudiahdz)8e1869e27
update marked dev dep (@claudiahdz)6a6151f37
[email protected]
(@claudiahdz)dc21422eb
[email protected]
(@claudiahdz)d341f88ce
[email protected]
(@claudiahdz)3e168d49b
[email protected]
(@claudiahdz)6ae942a51
[email protected]
(@claudiahdz)6a35e3dee
[email protected]
(@claudiahdz)6.14.6 (2020-07-07)
BUG FIXES
a9857b8f6
chore: remove auth info from logs (@claudiahdz)b7ad77598
#1416 fix: wrongnpm doctor
command result (@vanishcode)DEPENDENCIES
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
Commits
42e4625
6.14.7a81da2b
update AUTHORSe6e8d29
docs: changelog for 6.14.76a35e3d
[email protected]6ae942a
[email protected]3e168d4
[email protected]d341f88
[email protected]dc21422
[email protected]6fe2bdc
fix: npm ls --parseable --long output8788889
fix: gracefully handle error during npm install- 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)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)