Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🚨 [security] Update railties 7.0.8.1 → 7.1.3.2 (minor) #56

Merged
merged 2 commits into from
Feb 25, 2024
Merged

🚨 [security] Update railties 7.0.8.1 → 7.1.3.2 (minor) #56

merged 2 commits into from
Feb 25, 2024

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Feb 25, 2024

🚨 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?

✳️ railties (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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 (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Security Advisories 🚨

🚨 Possible XSS Vulnerability in Action Controller

There is a possible XSS vulnerability when using the translation helpers
(translate, t, etc) in Action Controller. This vulnerability has been
assigned the CVE identifier CVE-2024-26143.

Versions Affected: All. Not affected: None Fixed Versions: 7.1.3.1, 7.0.8.1

Impact

Applications using translation methods like translate, or t on a
controller, with a key ending in “_html”, a :default key which contains
untrusted user input, and the resulting string is used in a view, may be
susceptible to an XSS vulnerability.

For example, impacted code will look something like this:

class ArticlesController < ApplicationController
  def show
    @message = t("message_html", default: untrusted_input)
    # The `show` template displays the contents of `@message`
  end
end

To reiterate the pre-conditions, applications must:

  • Use a translation function from a controller (i.e. not I18n.t, or
    t from a view)
  • Use a key that ends in _html
  • Use a default value where the default value is untrusted and unescaped input
  • Send the text to the victim (whether that’s part of a template, or a
    render call)

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.

Workarounds

There are no feasible workarounds for this issue.

🚨 Possible ReDoS vulnerability in Accept header parsing in Action Dispatch

There is a possible ReDoS vulnerability in the Accept header parsing routines
of Action Dispatch. This vulnerability has been assigned the CVE identifier
CVE-2024-26142.

Versions Affected: >= 7.1.0, < 7.1.3.1 Not affected: < 7.1.0 Fixed Versions: 7.1.3.1

Impact

Carefully crafted Accept headers can cause Accept header parsing in
Action Dispatch to take an unexpected amount of time, possibly resulting in a
DoS vulnerability. All users running an affected release should either upgrade
or use one of the workarounds immediately.

Ruby 3.2 has mitigations for this problem, so Rails applications using
Ruby 3.2 or newer are unaffected.

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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 (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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 (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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 (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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 (7.0.8.1 → 7.1.3.2) · Repo · Changelog

Release Notes

7.1.3.2 (from changelog)

More info than we can show here.

7.1.3.1 (from changelog)

More info than we can show here.

7.1.3 (from changelog)

More info than we can show here.

7.1.2 (from changelog)

More info than we can show here.

7.1.1 (from changelog)

More info than we can show here.

7.1.0 (from changelog)

More info than we can show here.

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.

↗️ base64 (indirect, 0.1.1 → 0.2.0) · Repo

Release Notes

0.2.0

More info than we can show here.

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.

↗️ ipaddr (indirect, 1.2.5 → 1.2.6) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ json (indirect, 2.6.2 → 2.7.1) · Repo · Changelog

Release Notes

2.7.1

More info than we can show here.

2.7.0

More info than we can show here.

2.6.3

More info than we can show here.

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-protocol (indirect, 0.1.3 → 0.2.2) · Repo

Release Notes

0.2.2

More info than we can show here.

0.2.1

More info than we can show here.

0.2.0

More info than we can show here.

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.

↗️ openssl (indirect, 2.2.2 → 2.2.3) · Repo · Changelog

Release Notes

2.2.3

More info than we can show here.

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.8.1 → 3.0.9.1) · Repo · Changelog

Security Advisories 🚨

🚨 Possible Denial of Service Vulnerability in Rack Header Parsing

There is a possible denial of service vulnerability in the header parsing
routines in Rack. This vulnerability has been assigned the CVE identifier
CVE-2024-26146.

Versions Affected: All. Not affected: None Fixed Versions: 2.0.9.4, 2.1.4.4, 2.2.8.1, 3.0.9.1

Impact

Carefully crafted headers can cause header parsing in Rack to take longer than
expected resulting in a possible denial of service issue. Accept and
Forwarded headers are impacted.

Ruby 3.2 has mitigations for this problem, so Rack applications using
Ruby 3.2 or newer are unaffected.

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

🚨 Denial of Service Vulnerability in Rack Content-Type Parsing

There is a possible denial of service vulnerability in the content type
parsing component of Rack. This vulnerability has been assigned the CVE
identifier CVE-2024-25126.

Versions Affected: >= 0.4 Not affected: < 0.4 Fixed Versions: 3.0.9.1, 2.2.8.1

Impact

Carefully crafted content type headers can cause Rack’s media type parser to
take much longer than expected, leading to a possible denial of service
vulnerability.

Impacted code will use Rack’s media type parser to parse content type headers.
This code will look like below:

request.media_type

OR


request.media_type_params


OR


Rack::MediaType.type(content_type)

Some frameworks (including Rails) call this code internally, so upgrading is
recommended!

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.

Workarounds

There are no feasible workarounds for this issue.

🚨 Possible DoS Vulnerability with Range Header in Rack

There is a possible DoS vulnerability relating to the Range request header in
Rack. This vulnerability has been assigned the CVE identifier CVE-2024-26141.

Versions Affected: >= 1.3.0. Not affected: < 1.3.0 Fixed Versions: 3.0.9.1, 2.2.8.1

Impact

Carefully crafted Range headers can cause a server to respond with an
unexpectedly large response. Responding with such large responses could lead
to a denial of service issue.

Vulnerable applications will use the Rack::File middleware or the
Rack::Utils.byte_ranges methods (this includes Rails applications).

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

🚨 Possible Denial of Service Vulnerability in Rack’s header parsing

There is a denial of service vulnerability in the header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27539.

Versions Affected: >= 2.0.0 Not affected: None. Fixed Versions: 2.2.6.4, 3.0.6.1

Impact

Carefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted.

Workarounds

Setting Regexp.timeout in Ruby 3.2 is a possible workaround.

🚨 Possible DoS Vulnerability in Multipart MIME parsing

There is a possible DoS vulnerability in the Multipart MIME parsing code in Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27530.

Versions Affected: All. Not affected: None Fixed Versions: 3.0.4.2, 2.2.6.3, 2.1.4.3, 2.0.9.3

Impact

The Multipart MIME parsing code in Rack limits the number of file parts, but does not limit the total number of parts that can be uploaded. Carefully crafted requests can abuse this and cause multipart parsing to take longer than expected.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Workarounds

A proxy can be configured to limit the POST body size which will mitigate this issue.

🚨 Denial of service via header parsing in Rack

There is a possible denial of service vulnerability in the Range header
parsing component of Rack. This vulnerability has been assigned the CVE
identifier CVE-2022-44570.

Versions Affected: >= 1.5.0
Not affected: None.
Fixed Versions: 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1

Impact

Carefully crafted input can cause the Range header parsing component in Rack
to take an unexpected amount of time, possibly resulting in a denial of
service attack vector. Any applications that deal with Range requests (such
as streaming applications, or applications that serve files) may be impacted.

Workarounds

There are no feasible workarounds for this issue.

🚨 Denial of service via multipart parsing in Rack

There is a denial of service vulnerability in the multipart parsing component
of Rack. This vulnerability has been assigned the CVE identifier
CVE-2022-44572.

Versions Affected: >= 2.0.0
Not affected: None.
Fixed Versions: 2.0.9.2, 2.1.4.2, 2.2.6.1, 3.0.4.1

Impact

Carefully crafted input can cause RFC2183 multipart boundary parsing in Rack
to take an unexpected amount of time, possibly resulting in a denial of
service attack vector. Any applications that parse multipart posts using
Rack (virtually all Rails applications) are impacted.

Workarounds

There are no feasible workarounds for this issue.

🚨 Denial of Service Vulnerability in Rack Content-Disposition parsing

There is a denial of service vulnerability in the Content-Disposition parsing
component of Rack. This vulnerability has been assigned the CVE identifier
CVE-2022-44571.

Versions Affected: >= 2.0.0
Not affected: None.
Fixed Versions: 2.0.9.2, 2.1.4.2, 2.2.6.1, 3.0.4.1

Impact

Carefully crafted input can cause Content-Disposition header parsing in Rack
to take an unexpected amount of time, possibly resulting in a denial of
service attack vector. This header is used typically used in multipart
parsing. Any applications that parse multipart posts using Rack (virtually
all Rails applications) are impacted.

Workarounds

There are no feasible workarounds for this issue.

Release Notes

3.0.9.1

More info than we can show here.

3.0.9

More info than we can show here.

3.0.8

More info than we can show here.

3.0.7

More info than we can show here.

3.0.6.1 (from changelog)

More info than we can show here.

3.0.4.1

More info than we can show here.

3.0.2

More info than we can show here.

3.0.0 (from changelog)

More info than we can show here.

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.

↗️ securerandom (indirect, 0.2.0 → 0.3.1) · Repo

Release Notes

0.3.1

More info than we can show here.

0.3.0

More info than we can show here.

0.2.2

More info than we can show here.

0.2.1

More info than we can show here.

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.

↗️ timeout (indirect, 0.3.0 → 0.4.1) · Repo

Release Notes

0.4.1

More info than we can show here.

0.4.0

More info than we can show here.

0.3.2

More info than we can show here.

0.3.1

More info than we can show here.

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.

↗️ uri (indirect, 0.11.2 → 0.13.0) · Repo

Security Advisories 🚨

🚨 ReDoS vulnerability in URI

We have released the uri gem version 0.12.2, 0.10.3 that has a
security fix for a ReDoS vulnerability. This vulnerability has
been assigned the CVE identifier CVE-2023-36617.

Details

A ReDoS issue was discovered in the URI component through 0.12.1
for Ruby. The URI parser mishandles invalid URLs that have specific
characters. There is an increase in execution time for parsing
strings to URI objects with rfc2396_parser.rb and rfc3986_parser.rb.

NOTE: this issue exists becuse of an incomplete fix for CVE-2023-28755.

The uri gem version 0.12.1 and all versions prior 0.12.1 are
vulnerable for this vulnerability.

Recommended action

We recommend to update the uri gem to 0.12.2.
In order to ensure compatibility with bundled version in older
Ruby series, you may update as follows instead:

  • For Ruby 3.0: Update to uri 0.10.3

  • For Ruby 3.1 and 3.2: Update to uri 0.12.2
    You can use gem update uri to update it. If you are using bundler,
    please add gem "uri", ">= 0.12.2" (or other version mentioned
    above) to your Gemfile.

  • Affected versions: uri gem 0.12.1 or before

🚨 Ruby URI component ReDoS issue

A ReDoS issue was discovered in the URI component through 0.12.0 in
Ruby through 3.2.1. The URI parser mishandles invalid URLs that have
specific characters. It causes an increase in execution time for parsing
strings to URI objects. The fixed versions are 0.12.1, 0.11.1,
0.10.2 and 0.10.0.1.

Release Notes

0.13.0

More info than we can show here.

0.12.1

More info than we can show here.

0.12.0

More info than we can show here.

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.

🆕 bigdecimal (added, 3.1.6)

🆕 connection_pool (added, 2.4.1)

🆕 drb (added, 2.2.0)

🆕 io-console (added, 0.7.2)

🆕 irb (added, 1.11.2)

🆕 mutex_m (added, 0.2.0)

🆕 psych (added, 5.1.2)

🆕 rack-session (added, 2.0.0)

🆕 rackup (added, 2.1.0)

🆕 rdoc (added, 6.6.2)

🆕 reline (added, 0.4.2)

🆕 ruby2_keywords (added, 0.0.5)

🆕 stringio (added, 3.1.0)

🆕 webrick (added, 1.8.1)

🗑️ method_source (removed)

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)

@depfu depfu bot added the depfu label Feb 25, 2024
@depfu depfu bot merged commit 391c4b0 into main Feb 25, 2024
2 checks passed
@depfu depfu bot deleted the depfu/update/group/rails-7.1.3.2 branch February 25, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@12joan