🚨 [security] [ruby] Update all of rails: 7.0.3 → 7.0.3.1 (minor)

🚨 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.3 → 7.0.3.1) · Repo

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ actioncable (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ actionmailbox (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

↗️ actionmailer (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ actionpack (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ actiontext (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ actionview (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ activejob (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ activemodel (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ activerecord (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Security Advisories 🚨

🚨 Possible RCE escalation bug with Serialized Columns in Active Record

There is a possible escalation to RCE when using YAML serialized columns in
Active Record. This vulnerability has been assigned the CVE identifier
CVE-2022-32224.

Versions Affected: All.
Not affected: None
Fixed Versions: 7.0.3.1, 6.1.6.1, 6.0.5.1, 5.2.8.1

Impact

When serialized columns that use YAML (the default) are deserialized, Rails
uses YAML.unsafe_load to convert the YAML data in to Ruby objects. If an
attacker can manipulate data in the database (via means like SQL injection),
then it may be possible for the attacker to escalate to an RCE.

Impacted Active Record models will look something like this:
class User < ApplicationRecord
  serialize :options       # Vulnerable: Uses YAML for serialization
  serialize :values, Array # Vulnerable: Uses YAML for serialization
  serialize :values, JSON  # Not vulnerable
end
All users running an affected release should either upgrade or use one of the
workarounds immediately.

Releases

The FIXED releases are available at the normal locations.

The released versions change the default YAML deserializer to use
YAML.safe_load, which prevents deserialization of possibly dangerous
objects. This may introduce backwards compatibility issues with existing
data.

In order to cope with that situation, the released version also contains two
new Active Record configuration options. The configuration options are as
follows:

config.active_storage.use_yaml_unsafe_load

When set to true, this configuration option tells Rails to use the old
"unsafe" YAML loading strategy, maintaining the existing behavior but leaving
the possible escalation vulnerability in place. Setting this option to true
is not recommended, but can aid in upgrading.

config.active_record.yaml_column_permitted_classes

The "safe YAML" loading method does not allow all classes to be deserialized
by default. This option allows you to specify classes deemed "safe" in your
application. For example, if your application uses Symbol and Time in
serialized data, you can add Symbol and Time to the allowed list as follows:
config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
Workarounds

There are no feasible workarounds for this issue, but other coders (such as
JSON) are not impacted.

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ activestorage (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ activesupport (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

↗️ i18n (indirect, 1.10.0 → 1.11.0) · Repo · Changelog

Release Notes

1.11.0

What's Changed

Consistently return array from bulk lookup, even if translation(s) missing by @sambostock in #628

Fix typos by @movermeyer in #631

Add support for CLDR data in I18n::Backend::Pluralization by @movermeyer in #630

New Contributors

@sambostock made their first contribution in #628

Full Changelog: v1.10.0...v1.11.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 17 commits:

↗️ nokogiri (indirect, 1.13.6 → 1.13.7) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 11 commits:

↗️ railties (indirect, 7.0.3 → 7.0.3.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 3 commits:

Depfu Status

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)

carbonfive / raygun-rails