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.

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

Update dependency rack to v2.2.8.1 [SECURITY] #469

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rack (changelog) '2.2.8' -> '2.2.8.1' age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-26146

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.

Patches

To aid users who aren't able to upgrade immediately we have provided patches for
the two supported release series. They are in git-am format and consist of a
single changeset.

  • 2-0-header-redos.patch - Patch for 2.0 series
  • 2-1-header-redos.patch - Patch for 2.1 series
  • 2-2-header-redos.patch - Patch for 2.2 series
  • 3-0-header-redos.patch - Patch for 3.0 series

Credits

Thanks to svalkanov for reporting this and
providing patches!

CVE-2024-26141

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.

Patches

To aid users who aren't able to upgrade immediately we have provided patches for
the two supported release series. They are in git-am format and consist of a
single changeset.

  • 3-0-range.patch - Patch for 3.0 series
  • 2-2-range.patch - Patch for 2.2 series

Credits

Thank you ooooooo_q for the report and
patch

CVE-2024-25126

Summary

module Rack
  class MediaType
    SPLIT_PATTERN = %r{\s*[;,]\s*}

The above regexp is subject to ReDos. 50K blank characters as a prefix to the header will take over 10s to split.

PoC

A simple HTTP request with lots of blank characters in the content-type header:

request["Content-Type"] = (" " * 50_000) + "a,"

Impact

It's a very easy to craft ReDoS. Like all ReDoS the impact is debatable.


Release Notes

rack/rack (rack)

v2.2.8.1

Compare Source

What's Changed

Full Changelog: rack/rack@v2.2.8...v2.2.8.1


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/rubygems-rack-vulnerability branch from ff93203 to a2b368e Compare March 5, 2024 12:36
@renovate renovate bot force-pushed the renovate/rubygems-rack-vulnerability branch from a2b368e to 98225e0 Compare March 24, 2024 15:05
@renovate renovate bot changed the title Update dependency rack to v2.2.8.1 [SECURITY] Update dependency rack to v2.2.8.1 [SECURITY] - autoclosed Jul 10, 2024
@renovate renovate bot closed this Jul 10, 2024
@renovate renovate bot deleted the renovate/rubygems-rack-vulnerability branch July 10, 2024 01:41
@renovate renovate bot restored the renovate/rubygems-rack-vulnerability branch July 14, 2024 10:03
@renovate renovate bot changed the title Update dependency rack to v2.2.8.1 [SECURITY] - autoclosed Update dependency rack to v2.2.8.1 [SECURITY] Jul 14, 2024
@renovate renovate bot reopened this Jul 14, 2024
@renovate renovate bot force-pushed the renovate/rubygems-rack-vulnerability branch from 98225e0 to 4948372 Compare July 14, 2024 10:04
@renovate renovate bot force-pushed the renovate/rubygems-rack-vulnerability branch from 4948372 to ea9cfdf Compare July 15, 2024 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants