sequencescape
sequencescape copied to clipboard
π¨ [security] [ruby] Update rails 6.1.7.8 β 6.1.7.10 (patch)
π¨ 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?
β³οΈ rails (6.1.7.8 β 6.1.7.10) Β· Repo
Release Notes
6.1.7.10
Active Support
- No changes.
Active Model
- No changes.
Active Record
- No changes.
Action View
- No changes.
Action Pack
- No changes.
Active Job
- No changes.
Action Mailer
Fix NoMethodError in
block_format
helperMichael Leimstaedtner
Action Cable
- No changes.
Active Storage
- No changes.
Action Mailbox
- No changes.
Action Text
- No changes.
Railties
- No changes.
Guides
- No changes.
6.1.7.9
Active Support
- No changes.
Active Model
- No changes.
Active Record
- No changes.
Action View
- No changes.
Action Pack
Avoid regex backtracking in HTTP Token authentication
Avoid regex backtracking in query parameter filtering
Active Job
- No changes.
Action Mailer
Avoid regex backtracking in
block_format
helperAction Cable
- No changes.
Active Storage
- No changes.
Action Mailbox
- No changes.
Action Text
Avoid backtracing in plain_text_for_blockquote_node
Railties
- No changes.
Guides
- No changes.
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.
βοΈ actioncable (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ actionmailbox (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
βοΈ actionmailer (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Security Advisories π¨
π¨ Possible ReDoS vulnerability in block_format in Action Mailer
There is a possible ReDoS vulnerability in the block_format helper in Action Mailer. This vulnerability has been assigned the CVE identifier CVE-2024-47889.
Impact
Carefully crafted text can cause the block_format helper to take an unexpected amount of time, possibly resulting in a DoS vulnerability. All users running an affected release should either upgrade or apply the relevant patch immediately.
Ruby 3.2 has mitigations for this problem, so Rails applications using Ruby 3.2 or newer are unaffected. Rails 8.0.0.beta1 requires Ruby 3.2 or greater so is unaffected.
Releases
The fixed releases are available at the normal locations.
Workarounds
Users can avoid calling the
block_format
helper or upgrade to Ruby 3.2Credits
Thanks to ooooooo_q for the report!
Release Notes
6.1.7.10 (from changelog)
Fix NoMethodError in
block_format
helperMichael Leimstaedtner
6.1.7.9 (from changelog)
Avoid regex backtracking in
block_format
helper
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.
βοΈ actionpack (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Security Advisories π¨
π¨ Possible ReDoS vulnerability in HTTP Token authentication in Action Controller
There is a possible ReDoS vulnerability in Action Controller's HTTP Token authentication. This vulnerability has been assigned the CVE identifier CVE-2024-47887.
Impact
For applications using HTTP Token authentication via
authenticate_or_request_with_http_token
or similar, a carefully crafted header may cause header parsing to take an unexpected amount of time, possibly resulting in a DoS vulnerability. All users running an affected release should either upgrade or apply the relevant patch immediately.Ruby 3.2 has mitigations for this problem, so Rails applications using Ruby 3.2 or newer are unaffected. Rails 8.0.0.beta1 depends on Ruby 3.2 or greater so is unaffected.
Releases
The fixed releases are available at the normal locations.
Workarounds
Users on Ruby 3.2 are unaffected by this issue.
Credits
Thanks to scyoon for reporting
π¨ Possible ReDoS vulnerability in query parameter filtering in Action Dispatch
There is a possible ReDoS vulnerability in the query parameter filtering routines of Action Dispatch. This vulnerability has been assigned the CVE identifier CVE-2024-41128.
Impact
Carefully crafted query parameters can cause query parameter filtering to take an unexpected amount of time, possibly resulting in a DoS vulnerability. All users running an affected release should either upgrade or apply the relevant patch immediately.
Ruby 3.2 has mitigations for this problem, so Rails applications using Ruby 3.2 or newer are unaffected. Rails 8.0.0.beta1 depends on Ruby 3.2 or greater so is unaffected.
Releases
The fixed releases are available at the normal locations.
Workarounds
Users on Ruby 3.2 are unaffected by this issue.
Credits
Thanks to scyoon for the report and patches!
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
Avoid regex backtracking in HTTP Token authentication
Avoid regex backtracking in query parameter filtering
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.
βοΈ actiontext (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Security Advisories π¨
π¨ Possible ReDoS vulnerability in plain_text_for_blockquote_node in Action Text
There is a possible ReDoS vulnerability in the plain_text_for_blockquote_node helper in Action Text. This vulnerability has been assigned the CVE identifier CVE-2024-47888.
Impact
Carefully crafted text can cause the plain_text_for_blockquote_node helper to take an unexpected amount of time, possibly resulting in a DoS vulnerability. All users running an affected release should either upgrade or apply the relevant patch immediately.
Ruby 3.2 has mitigations for this problem, so Rails applications using Ruby 3.2 or newer are unaffected. Rails 8.0.0.beta1 depends on Ruby 3.2 or greater so is unaffected.
Releases
The fixed releases are available at the normal locations.
Workarounds
Users can avoid calling
plain_text_for_blockquote_node
or upgrade to Ruby 3.2Credits
Thanks to ooooooo_q for the report!
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
Avoid backtracing in plain_text_for_blockquote_node
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.
βοΈ actionview (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ activejob (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ activemodel (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ activerecord (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ activestorage (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ activesupport (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ loofah (indirect, 2.22.0 β 2.23.0) Β· Repo Β· Changelog
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
βοΈ net-imap (indirect, 0.4.14 β 0.5.0) Β· Repo
Release Notes
0.5.0
What's Changed
Breaking Changes
- π₯ Drop ruby 2.7 and 3.0 support, and require ruby 3.1 by @nevans in #276
- π₯β‘ Simplify
header-fld-name
parser (backward incompatible) by @nevans in #216
For example,HEADER.FIELDS(Content-Type)
orHEADER.FIELDS("Content-Type")
are semantically identical, and a server may choose to return the quoted version.
- Before this change, the FetchData attr header name would be quoted if the server sent the field name quoted.
- After this change, the header field names will always be unquoted by the parser, so the result will always available via
fetch_data.header_fields("Content-Type")
orfetch_data.attr_upcase["HEADER.FIELDS(CONTENT-TYPE)"]
.- π₯ Replace MessageSet with SequenceSet by @nevans in #282
Most of the changes are bugfixes or allow something new to work that didn't work before. See the PR for more details.
This affects#search
,#uid_search
,#sort
,#uid_sort
,#fetch
,#uid_fetch
,#store
,#uid_store
,#copy
,#uid_copy
,#move
,#uid_move
, and#uid_expunge
.- π₯ SequenceSet input validation for Set, Array, and enumerables by @nevans in #319
- Array inputs can still be deeply nested.
- Set inputs can only contain integers and
"*"
or:*
, to be consistent withSequenceSet#to_set
.- Other
Enumerables
will only be converted if they implement#to_sequence_set
.- π₯ Remove deprecated
#client_thread
attr_reader by @nevans in #321
#client_thread
was deprecated byv0.4.0
.- π₯ Drop deprecated BodyType structs by @nevans in #323
These structs were deprecated byv0.4.0
.Added
- β¨ Add
#extract_responses
method by @nevans in #330 Also backported tov0.4.17
.- β¨ New config option to return frozen dup from
#responses
by @nevans in #334 Also backported tov0.4.17
.- π₯ Improve SequenceSet frozen errors by @nevans in #331 Also backported to
v0.4.17
.- π SequenceSet API is considered stable now by @nevans in #318
- π Enforce
LOGINDISABLED
requirement by @nevans in #307
To workaround buggy servers,config.enforce_logindisabled
can be set to:when_capabilities_cached
orfalse
.- π SASL DIGEST-MD5: realm, host, service_name, etc by @nevans in #284
Please note that theDIGEST-MD5
SASL mechanism is insecure and deprecated.Deprecations
- π Warn about deprecated
#responses
usage by @nevans in #97
To silence these warnings:
- pass a block to
#responses
(supported sincev0.4.0
),- pass a response type to
#responses
for a frozen copied array (sincev0.4.17
),- set
config.responses_without_block
to:silence_deprecation_warning
(sincev0.4.13
),- set
config.responses_without_block
to:frozen_dup
for a frozen copy (sincev0.4.17
),- use
#clear_responses
instead (sincev0.4.0
),- use
#extract_responses
instead (sincev0.4.17
).- ποΈ Deprecate
MessageSet
by @nevans in #282
MessageSet
was only intended for internal use, and all internal usage has been replaced.Fixed
- π Fix #send_data to send DateTime as time by @taku0 in #313
Also backported tov0.4.15
.- π Fix #header_fld_name to handle quoted strings correctly by @taku0 in #315
Also backported tov0.4.16
.- π Fix SequenceSet[input] when input is a SequenceSet by @nevans in #326
Also backported tov0.4.17
.- π Fix Set inputs for SequenceSet by @nevans in #332
This bug was introduced by #319, which had not been previously released.Other Changes
- π§ Update default config for v0.5 by @nevans in #305
- β»οΈ Use Integer.try_convert (new in ruby 3.1+) by @nevans in #316
- ποΈ Add
category: :deprecated
to calls towarn
by @nevans in #322- β»οΈ Extract SASL::Authenticators#normalize_name by @nevans in #309
- π π Improvements and docs for SASL::ClientAdapter by @nevans in #320
- β»οΈ Use SASL::ClientAdapter by @nevans in #194
Documentation
- π Update Config rdoc for v0.5 by @nevans in #306
- π Update SASL documentation by @nevans in #308
- π SequenceSet API is considered stable now by @nevans in #318
- π π Improvements and docs for SASL::ClientAdapter by @nevans in #320
Miscellaneous
- β Add a Mutex to FakeServer (for tests only) by @nevans in #317
Also backported tov0.4.17
.- β¬οΈ Bump step-security/harden-runner from 2.8.1 to 2.9.0 by @dependabot in #311
- β¬οΈ Bump step-security/harden-runner from 2.9.0 to 2.9.1 by @dependabot in #312
- Bump step-security/harden-runner from 2.9.1 to 2.10.1 by @dependabot in #325
- π¨π Fix rdoc => ghpages workflow by @nevans in #335
- β Fix GH action for rubygems Trusted Publishing by @nevans in #340
Also backported tov0.4.17
.- β Setup simplecov by @nevans in #328
New Contributors
Full Changelog: v0.4.14...v0.5.0
(Note thatv0.4.x
releases sincev0.4.14
have used thev0.4-stable
branch.)
0.4.17
What's Changed
Added features
- β¨ Add
#extract_responses
method by @nevans in #337 (backports #330)- β¨ New config option to return frozen dup from
#responses
by @nevans in #339 (backports #334)
This will become the default inv0.6.0
.Bug fixes
Other Changes
Miscellaneous
- β Add a Mutex to FakeServer (for tests only) by @nevans in #336 (backports #317)
- β Fix GH action for Rubygems Trusted Publishing by @nevans in #341 (backports #340)
Full Changelog: v0.4.16...v0.4.17
0.4.16
What's Changed
Fixed
Full Changelog: v0.4.15...v0.4.16
0.4.15
What's Changed
Fixed
New Contributors
Full Changelog: v0.4.14...v0.4.15
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.
βοΈ rack (indirect, 2.2.9 β 2.2.10) Β· Repo Β· Changelog
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
βοΈ railties (indirect, 6.1.7.8 β 6.1.7.10) Β· Repo Β· Changelog
Release Notes
6.1.7.10 (from changelog)
- No changes.
6.1.7.9 (from changelog)
- No changes.
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.
βοΈ sprockets-rails (indirect, 3.5.1 β 3.5.2) Β· Repo Β· Changelog
Release Notes
3.5.2
What's Changed
- Fix deprecations with Rails 8.0 by @rafaelfranca in #535
New Contributors
Full Changelog: v3.5.1...v3.5.2
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.
βοΈ zeitwerk (indirect, 2.6.18 β 2.7.1) Β· Repo Β· Changelog
Release Notes
2.7.1 (from changelog)
Micro-optimization in a hot path.
Raises
Zeitwerk::Error
if an autoloaded constant expected to represent a namespace does not store a class or module object.Adds
truffleruby-head
to CI, except for autoloading thread-safety (see why in oracle/truffleruby#2431).
2.7.0 (from changelog)
Explicit namespaces can now also be defined using constant assignments.
While constant assignments like
# coordinates.rbCoordinates = Data.define(:x, :y)
worked for most objects, they did not for classes and modules that were also namespaces (i.e., those defined by a file and matching subdirectories). In such cases, their child constants could not be autoloaded.
This limitation has been removed.
TracePoint
is no longer used.Requires Ruby 3.2 or later.
Gems that work with previous versions of Zeitwerk also work with this one. If they support Ruby versions older than 3.2 they can specify a relaxed version constraint for Zeitwerk like "~> 2.6", for example.
In client projects, Bundler takes the Ruby requirement into account when resolving dependencies, so
Gemfile.lock
will get one compatible with the Ruby version being used.
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
- @β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 cancel merge
- Cancels automatic merging of this PR
- @β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)