Skip to content

Conversation

@Dustin4444
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 10 vulnerabilities in the rubygems dependencies of this project.

Snyk changed the following file(s):

  • Gemfile
⚠️ Warning
Failed to update the Gemfile.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Arbitrary Code Injection
SNYK-RUBY-GRAPHQL-9403760
  674  
high severity Allocation of Resources Without Limits or Throttling
SNYK-RUBY-RACK-10074187
  649  
high severity Relative Path Traversal
SNYK-RUBY-RACK-9398129
  649  
medium severity Web Cache Poisoning
SNYK-RUBY-RACK-1061917
  616  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-9510795
  576  
medium severity Improper Output Neutralization for Logs
SNYK-RUBY-RACK-9058602
  559  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-9510789
  469  
low severity Buffer Under-read
SNYK-RUBY-NOKOGIRI-9789079
  426  
low severity Race Condition
SNYK-RUBY-RACK-10074188
  329  
low severity Improper Removal of Sensitive Information Before Storage or Transfer
SNYK-RUBY-URI-9056162
  319  

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:

🦉 Arbitrary Code Injection
🦉 Use After Free
🦉 Allocation of Resources Without Limits or Throttling
🦉 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.

3 participants