Skip to content
This repository has been archived by the owner on Mar 10, 2022. It is now read-only.

🚨 [security] Update rack-protection: 1.5.3 → 1.5.5 (patch) #3

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

🚨 [security] Update rack-protection: 1.5.3 → 1.5.5 (patch) #3

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Feb 15, 2019 •
edited
Loading

🚨 Your version of rack-protection has known security vulnerabilities 🚨

Advisory: CVE-2018-1000119
Disclosed: March 07, 2018
URL: https://github.com/sinatra/rack-protection/pull/98

rack-protection gem timing attack vulnerability when validating CSRF token

Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains
a timing attack vulnerability in the CSRF token checking that can result in signatures
can be exposed. This attack appear to be exploitable via network connectivity to
the ruby application.


🚨 We recommend to merge and deploy this update as soon as possible! 🚨

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ rack-protection (indirect, 1.5.3 → 1.5.5) · Repo · Changelog

↗️ rack (indirect, 1.6.4 → 1.6.11) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 29 commits:

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Circle CI, Semaphore and Travis-CI are all excellent options.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 15, 2019
@depfu depfu bot changed the title 🚨 [security] Update rack-protection: 1.5.3 → 1.5.5 (patch) 🚨 [security] Update rack-protection: 1.5.3 → 1.5.5 (patch) Jul 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants