🚨 [security] Update rails 7.0.8.4 → 7.0.8.6 (patch)

[depfu]

---

🚨 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 (7.0.8.4 → 7.0.8.6) · Repo

Release Notes

7.0.8.6

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 helper

  Michael Leimstaedtner

Action Cable

• No changes.

Active Storage

• No changes.

Action Mailbox

• No changes.

Action Text

• No changes.

Railties

• No changes.

Guides

• No changes.

7.0.8.5

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

  [CVE-2024-47887]

• Avoid regex backtracking in query parameter filtering

  [CVE-2024-41128]

Active Job

• No changes.

Action Mailer

• Avoid regex backtracking in block_format helper

  [CVE-2024-47889]

Action Cable

• No changes.

Active Storage

• No changes.

Action Mailbox

• No changes.

Action Text

• Avoid backtracing in plain_text_for_blockquote_node

  [CVE-2024-47888]

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.

✳️ net-imap (0.4.16 → 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) or HEADER.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") or fetch_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 with SequenceSet#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 by v0.4.0.
• 🔥 Drop deprecated BodyType structs by @nevans in #323
  These structs were deprecated by v0.4.0.

Added

• ✨ Add #extract_responses method by @nevans in #330 Also backported to v0.4.17.
• ✨ New config option to return frozen dup from #responses by @nevans in #334 Also backported to v0.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 or false.
• 🔒 SASL DIGEST-MD5: realm, host, service_name, etc by @nevans in #284
  Please note that the DIGEST-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 since v0.4.0),
  • pass a response type to #responses for a frozen copied array (since v0.4.17),
  • set config.responses_without_block to :silence_deprecation_warning (since v0.4.13),
  • set config.responses_without_block to :frozen_dup for a frozen copy (since v0.4.17),
  • use #clear_responses instead (since v0.4.0),
  • use #extract_responses instead (since v0.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 to v0.4.15.
• 🐛 Fix #header_fld_name to handle quoted strings correctly by @taku0 in #315
  Also backported to v0.4.16.
• 🐛 Fix SequenceSet[input] when input is a SequenceSet by @nevans in #326
  Also backported to v0.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 to warn 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 to v0.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 to v0.4.17.
• ✅ Setup simplecov by @nevans in #328

New Contributors

• @taku0 made their first contribution in #313

Full Changelog: v0.4.14...v0.5.0
(Note that v0.4.x releases since v0.4.14 have used the v0.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 in v0.6.0.

Bug fixes

• 🐛 Fix SequenceSet[input] when input is a SequenceSet by @nevans in #327 (backports #326)

Other Changes

• 🥅 Improve SequenceSet frozen errors by @nevans in #338 (backports #331)

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

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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

↗️ actionmailer (indirect, 7.0.8.4 → 7.0.8.6) · 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.2

Credits

Thanks to ooooooo_q for the report!

Release Notes

7.0.8.6 (from changelog)

• Fix NoMethodError in block_format helper

  Michael Leimstaedtner

7.0.8.5 (from changelog)

• Avoid regex backtracking in block_format helper

  [CVE-2024-47889]

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, 7.0.8.4 → 7.0.8.6) · 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

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (from changelog)

• Avoid regex backtracking in HTTP Token authentication

  [CVE-2024-47887]

• Avoid regex backtracking in query parameter filtering

  [CVE-2024-41128]

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, 7.0.8.4 → 7.0.8.6) · 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.2

Credits

Thanks to ooooooo_q for the report!

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (from changelog)

• Avoid backtracing in plain_text_for_blockquote_node

  [CVE-2024-47888]

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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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.

↗️ rack (indirect, 2.2.9 → 2.2.10) · Repo · Changelog

Release Notes

2.2.10 (from changelog)

• Fix compatibility issues with Ruby v3.4.0. (#2248, @byroot)

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.

↗️ railties (indirect, 7.0.8.4 → 7.0.8.6) · Repo · Changelog

Release Notes

7.0.8.6 (from changelog)

• No changes.

7.0.8.5 (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.

↗️ 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.rb

  Coordinates = 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)

[coveralls]

coverage: 98.313%. remained the same
when pulling 5a264a7 on depfu/update/group/rails-7.0.8.6
into 7634b3f on main.

[depfu]

Closing because this update has already been applied