🚨 [security] Update rack-cors: 1.0.2 → 1.0.6 (patch) #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 Your version of rack-cors has known security vulnerabilities 🚨
Advisory: CVE-2019-18978
Disclosed: November 15, 2019
URL: https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d
rack-cors directory traversal via path
🚨 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-cors (1.0.2 → 1.0.6) · Repo · Changelog
Release Notes
1.0.6 (from changelog)
1.0.5 (from changelog)
1.0.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
Use escape instead of escape_pathUp rack requirementUpdating Gems to hopefully get rid of alerts in GHReduce default max_age to a more sensible valueUnescape and resolve paths before resource checks[CI] Test against Ruby 2.6Version 1.0.3Clean up gemspecUpdate rack gemUpdate Rails4 exampleRemove unnecessary :require option from Gemfile exampleAdd an :if example to the README (based on https://github.com/cyu/rack-cors/issues/70#issuecomment-75392790)Remove CONTENT_TYPE constantremove content-type header from preflight responseUpdate rails4 example to 4.2.10Updated deps to fix more vulnerabilitiesUpdated Rails4 deps to fix vulnerabilitiesUpdated rack exampleRemoving Rails 3 exampleUpdating dev dependenciesTest PATCH supportAdd test for arrays of upstream Vary headersHandle arrays of vary headersfix readme typoUpdate README.md with ruby 1.9+ hash syntax[CI] Test against Ruby 2.4 and 2.5Add test coverage for loggerFixing some grammerzRename CHANGELOG to CHANGELOG.mdUpdate changelogDepfu 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