🚨 [security] Update rails 7.1.3.3 → 7.1.3.4 (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 (7.1.3.3 → 7.1.3.4) · Repo

Release Notes

7.1.3.4

Active Support

No changes.

Active Model

No changes.

Active Record

No changes.

Action View

No changes.

Action Pack

Include the HTTP Permissions-Policy on non-HTML Content-Types
[CVE-2024-28103]

Active Job

No changes.

Action Mailer

No changes.

Action Cable

No changes.

Active Storage

No changes.

Action Mailbox

No changes.

Action Text

Sanitize ActionText HTML ContentAttachment in Trix edit view
[CVE-2024-32464]

Railties

No changes.

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

Commits

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

↗️ actioncable (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ actionmailbox (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

↗️ actionmailer (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ actionpack (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Security Advisories 🚨

🚨 Missing security headers in Action Pack on non-HTML responses

Permissions-Policy is Only Served on HTML Content-Type

The application configurable Permissions-Policy is only served on responses
with an HTML related Content-Type.

This has been assigned the CVE identifier CVE-2024-28103.

Versions Affected: >= 6.1.0
Not affected: < 6.1.0
Fixed Versions: 6.1.7.8, 7.0.8.4, and 7.1.3.4

Impact

Responses with a non-HTML Content-Type are not serving the configured Permissions-Policy. There are certain non-HTML Content-Types that would benefit from having the Permissions-Policy enforced.

Releases

The fixed releases are available at the normal locations.

Workarounds

N/A

Patches

To aid users who aren't able to upgrade immediately we have provided patches for
the supported release series in accordance with our
maintenance policy
regarding security issues. They are in git-am format and consist of a
single changeset.

6-1-include-permissions-policy-header-on-non-html.patch - Patch for 6.1 series

7-0-include-permissions-policy-header-on-non-html.patch - Patch for 7.0 series

7-1-include-permissions-policy-header-on-non-html.patch - Patch for 7.1 series

Credits

Thank you shinkbr for reporting this!

Commits

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

↗️ actiontext (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Security Advisories 🚨

🚨 ActionText ContentAttachment can Contain Unsanitized HTML

Instances of ActionText::Attachable::ContentAttachment included within a rich_text_area tag could potentially contain unsanitized HTML.

This has been assigned the CVE identifier CVE-2024-32464.

Versions Affected: >= 7.1.0
Not affected: < 7.1.0
Fixed Versions: 7.1.3.4

Impact

This could lead to a potential cross site scripting issue within the Trix editor.

Releases

The fixed releases are available at the normal locations.

Workarounds

N/A

Patches

To aid users who aren't able to upgrade immediately we have provided patches for the supported release series in accordance with our maintenance policy regarding security issues. They are in git-am format and consist of a single changeset.

action_text_content_attachment_xss_7_1_stable.patch - Patch for 7.1 series

Credits

Thank you ooooooo_q for reporting this!

Commits

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

↗️ actionview (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ activejob (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ activemodel (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ activerecord (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ activestorage (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ activesupport (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

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

↗️ railties (indirect, 7.1.3.3 → 7.1.3.4) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 4 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 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)

stringer-rss / stringer