Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade @graphprotocol/graph-cli from 0.18.0 to 0.92.0 #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rmourey26
Copy link
Member

snyk-top-banner

Snyk has created this PR to fix 24 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916
  776  
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917
  776  
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918
  776  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303
  756  
high severity Improper Validation of Integrity Check Value
SNYK-JS-SECP256K1-8237220
  756  
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
  751  
high severity Prototype Pollution
SNYK-JS-ASYNC-2441827
  696  
high severity Uncontrolled resource consumption
SNYK-JS-BRACES-6838727
  696  
high severity Prototype Poisoning
SNYK-JS-QS-3153490
  696  
high severity Prototype Pollution
SNYK-JS-NODEFORGE-598677
  686  
high severity Code Injection
SNYK-JS-LODASH-1040724
  681  
medium severity Server-Side Request Forgery (SSRF)
SNYK-JS-IP-7148531
  646  
high severity Inadequate Encryption Strength
SNYK-JS-KEYPAIR-1730326
  644  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694
  629  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
  586  
medium severity Open Redirect
SNYK-JS-NODEFORGE-2330875
  586  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430339
  579  
medium severity Cryptographic Issues
SNYK-JS-ELLIPTIC-1064899
  554  
medium severity Information Exposure
SNYK-JS-NODEFETCH-2342118
  539  
medium severity Prototype Pollution
SNYK-JS-NODEFORGE-2331908
  529  
low severity Prototype Pollution
SNYK-JS-MINIMIST-2429795
  506  
low severity Regular Expression Denial of Service (ReDoS)
npm:debug:20170905
  506  
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430337
  494  
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430341
  494  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Uncontrolled resource consumption
🦉 Cryptographic Issues
🦉 More lessons are available in Snyk Learn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants