Skip to content

[Snyk] Fix for 1 vulnerabilities#9185

Closed
pauldoomgov wants to merge 1 commit intomainfrom
snyk-fix-1d99487c7e78d14460c597816c9c84d2
Closed

[Snyk] Fix for 1 vulnerabilities#9185
pauldoomgov wants to merge 1 commit intomainfrom
snyk-fix-1d99487c7e78d14460c597816c9c84d2

Conversation

@pauldoomgov
Copy link
Contributor

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


Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • Gemfile
    • Gemfile.lock

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 616/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Web Cache Poisoning
SNYK-RUBY-RACK-1061917
No Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.


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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

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

@aduth
Copy link
Contributor

aduth commented Sep 11, 2023

I think this is the same as #7193, though unclear if we'll also still want to handle the pending Rails upgrade. The other thing I notice here is that it's downgrading the Ruby version in Gemfile.lock, which I don't think we'll want.

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