Fix 9 npm dependencies #41
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![atomist[bot]](https://avatars.githubusercontent.com/in/407?s=60&v=4){kind=small}
atomist
bot
added
auto-branch-delete:on-close
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
8d7770d
to
d2ab04a
Compare
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
d2ab04a
to
8cf084b
Compare
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
8cf084b
to
11698ec
Compare
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
62333fa
to
41bf286
Compare
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
41bf286
to
3e0bf7a
Compare
npm audit fix updated the following npm dependencies: * ansi-regex > 5.0.1 * async > 3.2.3 * minimist > 1.2.6 * node-fetch > 2.6.7 * node-forge > 1.3.1 * re2 > 1.17.4 * tar > 6.1.11 * universal-analytics > 0.5.3 * vm2 > 3.9.9 [atomist:generated] [atomist-skill:atomist/npm-vulnerability-scanner-skill]
atomist
bot
force-pushed
the
atomist/npm-audit-main
branch
from
3e0bf7a
to
667c6ca
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes 2 critical and 1 high security vulnerabilities open on 54d105f but 8 high and 4 moderate vulnerabilities remain open and need manual review.
npm audit fixupdated the following npm dependencies:ansi-regex5.0.0 > 5.0.1async3.2.0 > 3.2.3minimist1.2.5 > 1.2.6node-fetch2.6.1 > 2.6.7node-forge1.2.1 > 1.3.1re23.0.0, 6.10.2 > 1.17.4tar6.0.5 > 6.1.11universal-analytics6.10.2 > 0.5.3vm23.9.5 > 3.9.9Fixed vulnerabilities
Following security vulnerabilities are fixed:
minimist
Prototype Pollution in minimist Upgrade to version 1.2.6 or later
critical ·
<1.2.6· CVE-2021-44906 · automatic fix availableminimist@1.2.5· 4 vulnerable pathsportfinder > mkdirp > minimistsuperstatic > update-notifier > latest-version > package-json > registry-auth-token > rc > minimistunzipper > fstream > mkdirp > minimistupdate-notifier > latest-version > package-json > registry-auth-token > rc > minimistvm2
Sandbox bypass in vm2 Upgrade to version 3.9.6 or later
critical ·
<3.9.6· CVE-2021-23555 · automatic fix availablevm2@3.9.5· 1 vulnerable pathproxy-agent > pac-proxy-agent > pac-resolver > degenerator > vm2async
Prototype Pollution in async Upgrade to version 3.2.2 or later
high ·
>=3.0.0 <3.2.2· CVE-2021-43138 · automatic fix availableasync@3.2.0· 1 vulnerable patharchiver > asyncnode-fetch
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor Upgrade to version 2.6.7 or later
high ·
<2.6.7· CVE-2022-0235 · automatic fix availablenode-fetch@2.6.1· 5 vulnerable paths@google-cloud/pubsub > google-auth-library > gaxios > node-fetch@google-cloud/pubsub > google-auth-library > gcp-metadata > gaxios > node-fetch@google-cloud/pubsub > google-gax > google-auth-library > gcp-metadata > gaxios > node-fetchgoogle-auth-library > gaxios > node-fetchnode-fetchnode-forge
Improper Verification of Cryptographic Signature in node-forge Upgrade to version 1.3.0 or later
high ·
<1.3.0· CVE-2022-24772 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgeImproper Verification of Cryptographic Signature in node-forge Upgrade to version 1.3.0 or later
high ·
<1.3.0· CVE-2022-24771 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgeImproper Verification of Cryptographic Signature in
node-forgeUpgrade to version 1.3.0 or latermoderate ·
<1.3.0· CVE-2022-24773 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgetar
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning Upgrade to version 6.1.2 or later
high ·
>=6.0.0 <6.1.2· CVE-2021-32803 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite due to insufficient absolute path sanitization Upgrade to version 6.1.1 or later
high ·
>=6.0.0 <6.1.1· CVE-2021-32804 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Upgrade to version 6.1.7 or later
high ·
>=6.0.0 <6.1.7· CVE-2021-37701 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization Upgrade to version 6.1.9 or later
high ·
>=6.0.0 <6.1.9· CVE-2021-37713 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Upgrade to version 6.1.9 or later
high ·
>=6.0.0 <6.1.9· CVE-2021-37712 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > taransi-regex
Inefficient Regular Expression Complexity in chalk/ansi-regex Upgrade to version 3.0.1 or later
moderate ·
>=3.0.0 <3.0.1· CVE-2021-3807 · automatic fix availableansi-regex@3.0.0· 1 vulnerable pathsuperstatic > re2 > node-gyp > npmlog > gauge > wide-align > string-width > strip-ansi > ansi-regexInefficient Regular Expression Complexity in chalk/ansi-regex Upgrade to version 5.0.1 or later
moderate ·
>=5.0.0 <5.0.1· CVE-2021-3807 · automatic fix availableansi-regex@5.0.0· 3 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > cliui > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > strip-ansi > ansi-regexansi-regex@5.0.0· 3 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > cliui > wrap-ansi > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > wrap-ansi > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > wrap-ansi > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 1 vulnerable pathsuperstatic > update-notifier > boxen > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable pathssuperstatic > update-notifier > boxen > widest-line > string-width > strip-ansi > ansi-regexupdate-notifier > boxen > widest-line > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable pathsupdate-notifier > boxen > string-width > strip-ansi > ansi-regexupdate-notifier > boxen > wrap-ansi > string-width > strip-ansi > ansi-regexajv
Prototype Pollution in Ajv Upgrade to version 6.12.3 or later
moderate ·
<6.12.3· CVE-2020-15366 · automatic fix availableajv@6.10.2· 3 vulnerable pathsrequest > har-validator > ajvsuperstatic > re2 > node-gyp > request > har-validator > ajvuniversal-analytics > request > har-validator > ajvOpen vulnerabilities
Following security vulnerabilities remain open and need manual review:
async
Prototype Pollution in async Upgrade to version 2.6.4 or later
high ·
<2.6.4· CVE-2021-43138 · automatic fix availableasync@2.6.3· 1 vulnerable pathportfinder > asyncasync@1.5.2· 1 vulnerable pathsuperstatic > nash > asyncnode-forge
Improper Verification of Cryptographic Signature in node-forge Upgrade to version 1.3.0 or later
high ·
<1.3.0· CVE-2022-24772 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgeImproper Verification of Cryptographic Signature in node-forge Upgrade to version 1.3.0 or later
high ·
<1.3.0· CVE-2022-24771 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgeImproper Verification of Cryptographic Signature in
node-forgeUpgrade to version 1.3.0 or latermoderate ·
<1.3.0· CVE-2022-24773 · automatic fix availablenode-forge@1.2.1· 3 vulnerable paths@google-cloud/pubsub > google-auth-library > gtoken > google-p12-pem > node-forge@google-cloud/pubsub > google-gax > google-auth-library > gtoken > google-p12-pem > node-forgegoogle-auth-library > gtoken > google-p12-pem > node-forgetar
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning Upgrade to version 6.1.2 or later
high ·
>=6.0.0 <6.1.2· CVE-2021-32803 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite due to insufficient absolute path sanitization Upgrade to version 6.1.1 or later
high ·
>=6.0.0 <6.1.1· CVE-2021-32804 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Upgrade to version 6.1.7 or later
high ·
>=6.0.0 <6.1.7· CVE-2021-37701 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization Upgrade to version 6.1.9 or later
high ·
>=6.0.0 <6.1.9· CVE-2021-37713 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > tarArbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Upgrade to version 6.1.9 or later
high ·
>=6.0.0 <6.1.9· CVE-2021-37712 · automatic fix availabletar@6.0.5· 1 vulnerable pathsuperstatic > re2 > node-gyp > taransi-regex
Inefficient Regular Expression Complexity in chalk/ansi-regex Upgrade to version 3.0.1 or later
moderate ·
>=3.0.0 <3.0.1· CVE-2021-3807 · automatic fix availableansi-regex@3.0.0· 1 vulnerable pathsuperstatic > re2 > node-gyp > npmlog > gauge > wide-align > string-width > strip-ansi > ansi-regexInefficient Regular Expression Complexity in chalk/ansi-regex Upgrade to version 5.0.1 or later
moderate ·
>=5.0.0 <5.0.1· CVE-2021-3807 · automatic fix availableansi-regex@5.0.0· 3 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > cliui > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > strip-ansi > ansi-regexansi-regex@5.0.0· 3 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > cliui > wrap-ansi > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > wrap-ansi > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > cliui > wrap-ansi > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable paths@google-cloud/pubsub > google-gax > @grpc/grpc-js > @grpc/proto-loader > yargs > string-width > strip-ansi > ansi-regex@google-cloud/pubsub > google-gax > @grpc/proto-loader > yargs > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 1 vulnerable pathsuperstatic > update-notifier > boxen > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable pathssuperstatic > update-notifier > boxen > widest-line > string-width > strip-ansi > ansi-regexupdate-notifier > boxen > widest-line > string-width > strip-ansi > ansi-regexansi-regex@5.0.0· 2 vulnerable pathsupdate-notifier > boxen > string-width > strip-ansi > ansi-regexupdate-notifier > boxen > wrap-ansi > string-width > strip-ansi > ansi-regexajv
Prototype Pollution in Ajv Upgrade to version 6.12.3 or later
moderate ·
<6.12.3· CVE-2020-15366 · automatic fix availableajv@6.10.2· 2 vulnerable pathsrequest > har-validator > ajvsuperstatic > re2 > node-gyp > request > har-validator > ajvFiles changed:
package-lock.jsonpackage.jsonatomist/npm-vulnerability-scanner-skill · Configure