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 rspec-rails from 6.1.2 to 6.1.3 #623

Closed
wants to merge 1 commit into from

Conversation

arthurashman
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

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

Snyk changed the following file(s):

  • Gemfile
  • Gemfile.lock

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Web Cache Poisoning
SNYK-RUBY-RACK-1061917
  616  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@arthurashman arthurashman requested a review from a team as a code owner June 20, 2024 00:55
@timpeat timpeat force-pushed the snyk-fix-c6ec4938a62162573403e4edfab779a8 branch from f21ee46 to 0120f2f Compare July 5, 2024 08:04
@timpeat
Copy link
Member

timpeat commented Jul 26, 2024

already done here: #653

@timpeat timpeat closed this Jul 26, 2024
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.

None yet

3 participants