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 graphiql-rails from 1.10.0 to 1.10.1 #126

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

SherfeyInv
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • pkgs/applications/version-management/gitlab/rubyEnv/Gemfile
⚠️ Warning
Failed to update the Gemfile.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Heap-based Buffer Overflow
SNYK-RUBY-NOKOGIRI-7164639
  696  
medium severity Web Cache Poisoning
SNYK-RUBY-RACK-1061917
  616  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-6228056
  524  

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:

🦉 Use After Free

@SherfeyInv SherfeyInv merged commit a0851a0 into master Aug 15, 2024
11 checks passed
@SherfeyInv SherfeyInv deleted the snyk-fix-654be7e5139cb7a0a3a385b65ba3a8ad branch August 15, 2024 22:37
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