🚨 [security] [ruby] Update activesupport: 7.0.4.2 → 7.0.4.3 (patch)
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?
↗ ️ activesupport (indirect, 7.0.4.2 → 7.0.4.3) · Repo · Changelog
Security Advisories 🚨
🚨 Possible XSS Security Vulnerability in SafeBuffer#bytesplice
There is a vulnerability in ActiveSupport if the new bytesplice method is called on a SafeBuffer with untrusted user input.
This vulnerability has been assigned the CVE identifier CVE-2023-28120.Versions Affected: All. Not affected: None Fixed Versions: 7.0.4.3, 6.1.7.3
Impact
ActiveSupport uses the SafeBuffer string subclass to tag strings as html_safe after they have been sanitized.
When these strings are mutated, the tag is should be removed to mark them as no longer being html_safe.Ruby 3.2 introduced a new bytesplice method which ActiveSupport did not yet understand to be a mutation.
Users on older versions of Ruby are likely unaffected.All users running an affected release and using bytesplice should either upgrade or use one of the workarounds immediately.
Workarounds
Avoid calling bytesplice on a SafeBuffer (html_safe) string with untrusted user input.
Release Notes
7.0.4.3 (from changelog)
Implement SafeBuffer#bytesplice
[CVE-2023-28120]
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
↗ ️ concurrent-ruby (indirect, 1.2.0 → 1.2.2) · Repo · Changelog
Release Notes
1.2.2
concurrent-ruby 1.2.2:
- (#993) Fix arguments passed to
Concurrent::Map
'sdefault_proc
.
1.2.1
concurrent-ruby 1.2.1:
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
Fix Concurrent::Map default_proc arguments
Prepare CHANGELOG for next version
1.2.1
Run isolated specs on the oldest CRuby too
Add CHANGELOG for https://github.com/ruby-concurrency/concurrent-ruby/pull/990
Revert "Prefer `Process.pid` over `$$`"
Add `require 'fiber'` for `Fiber.current` usage.
Prefer `Process.pid` over `$$`
Optimize Concurrent::Map#[] on CRuby by letting the backing Hash handle the default_proc
Modernize Concurrent::Map benchmark
Need `bundle install` before generating master docs
Make it easier to publish only edge
Bump version of edge too since there were changes
Give more time to join threads
Guard flaky assertion on JRuby
Fix docs generation for 1.2.0
↗ ️ minitest (indirect, 5.17.0 → 5.18.0) · Repo · Changelog
Release Notes
5.18.0 (from changelog)
2 major enhancements:
Added assert_pattern & refute_pattern for pattern matching. (flavorjones)
Added matching must_pattern_match & wont_pattern_match to minitest/spec.
1 bug fix:
Support the new message format of NameError in Ruby 3.3 (mame)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
prepped for release
! Added assert_pattern & refute_pattern for pattern matching. (flavorjones)
Fixed typo in doco. (ahangarha)
- Support the new message format of NameError in Ruby 3.3 (mame)
Add 2.6 to matrix... stays until some rails versions expire, sadly.
Adds Ruby 3.2 to the CI matrix. Also updates checkout action version. (petergoldstein)
Minor tweak to Rakefile to fix CI on older rubies
👉 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 Github Actions 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 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)