🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this 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.
add support for rubocop-rspec syntax extensions (#745)
2.2.0 (from changelog)
Fixed
Using policy_class and a namespaced record now passes only the record when instantiating the policy. (#697, #689, #694, #666)
Changed
Require users to explicitly define Scope#resolve in generated policies (#711, #722)
Deprecated
Deprecate include Pundit in favor of include Pundit::Authorization (#621)
2.1.1 (from changelog)
Friday 13th-release!
Careful! The bugfix below (#626) could break existing code. If you rely on the
return value for authorize and namespaced policies you might need to do some
changes.
Fixed
.authorize and #authorize return the instance, even for namespaced
policies (#626)
Changed
Generate application scope with protected attr_readers. (#616)
Removed
Dropped support for Ruby end-of-life versions: 2.1 and 2.2. (#604)
Dropped support for Ruby end-of-life versions: 2.3 (#633)
Dropped support for Ruby end-of-life versions: 2.4, 2.5 and JRuby 9.1 (#676)
1.0.0 to 1.2.9 when used with the Ruby data source (tzinfo-data).
Vulnerability
With the Ruby data source (the tzinfo-data gem for tzinfo version 1.0.0 and
later and built-in to earlier versions), time zones are defined in Ruby files.
There is one file per time zone. Time zone files are loaded with require on
demand. In the affected versions, TZInfo::Timezone.get fails to validate
time zone identifiers correctly, allowing a new line character within the
identifier. With Ruby version 1.9.3 and later, TZInfo::Timezone.get can be
made to load unintended files with require, executing them within the Ruby
process.
For example, with version 1.2.9, you can run the following to load a file with
path /tmp/payload.rb:
The exact number of parent directory traversals needed will vary depending on
the location of the tzinfo-data gem.
TZInfo versions 1.2.6 to 1.2.9 can be made to load files from outside of the
Ruby load path. Versions up to and including 1.2.5 can only be made to load
files from directories within the load path.
This could be exploited in, for example, a Ruby on Rails application using
tzinfo version 1.2.9, that allows file uploads and has a time zone selector
that accepts arbitrary time zone identifiers.
The CVSS score and severity have been set on this basis.
Versions 2.0.0 and later are not vulnerable.
Patches
Versions 0.3.61 and 1.2.10 include fixes to correctly validate time zone
identifiers.
Note that version 0.3.61 can still load arbitrary files from the Ruby load
path if their name follows the rules for a valid time zone identifier and the
file has a prefix of tzinfo/definition within a directory in the load path.
For example if /tmp/upload was in the load path, then TZInfo::Timezone.get('foo') could load a file with path /tmp/upload/tzinfo/definition/foo.rb. Applications should ensure that
untrusted files are not placed in a directory on the load path.
Workarounds
As a workaround, the time zone identifier can be validated before passing to TZInfo::Timezone.get by ensuring it matches the regular expression \\A[A-Za-z0-9+\\-_]+(?:\\/[A-Za-z0-9+\\-_]+)*\\z.
Fixed a relative path traversal bug that could cause arbitrary files to be loaded with require when used with RubyDataSource. Please refer to GHSA-5cm2-9h8c-rvfx for details. CVE-2022-31163.
Ignore the SECURITY file from Arch Linux's tzdata package. #134.
Fixed an incorrect InvalidTimezoneIdentifier exception raised when loading a zoneinfo file that includes rules specifying an additional transition to the final defined offset (for example, Africa/Casablanca in version 2018e of the Time Zone Database). #123.
Added support for handling "slim" format zoneinfo files that are produced by default by zic version 2020b and later. The POSIX-style TZ string is now used calculate DST transition times after the final defined transition in the file. The 64-bit section is now always used regardless of whether Time has support for 64-bit times. #120.
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 recreate
Recreates this PR, overwriting any edits that you've made to it
@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[bot]
commented
1 year ago
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this 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?
✳️ pundit (1.1.0 → 2.3.0) · Repo · Changelog
Release Notes
2.3.0 (from changelog)
2.2.0 (from changelog)
2.1.1 (from changelog)
2.1.0 (from changelog)
2.0.1 (from changelog)
Does any of this look wrong? Please let us know.
↗️ concurrent-ruby (indirect, 1.0.5 → 1.1.10) · Repo · Changelog
Release Notes
1.1.10
1.1.9 (from changelog)
1.1.8 (from changelog)
1.1.7 (from changelog)
1.1.6 (from changelog)
1.1.5 (from changelog)
1.1.4 (from changelog)
1.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ i18n (indirect, 1.1.0 → 1.12.0) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ minitest (indirect, 5.11.3 → 5.16.3) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ tzinfo (indirect, 1.2.5 → 1.2.10) · Repo · Changelog
Security Advisories 🚨
🚨 TZInfo relative path traversal vulnerability allows loading of arbitrary files
Release Notes
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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