CVE-2022-44572: High severity Rack Project Rack Ruby vulnerability

Published Jan 18, 2023
·
Updated

A denial of service vulnerability in the multipart parsing component of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1 and 3.0.0.1 could allow an attacker tocraft input that 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.

Other sources

Carefully crafted input can cause RFC2183 multipart boundary parsing in Rackto 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.

Red Hat

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.0.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. 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-Forbid-control-characters-in-attributes.patch - Patch for 2.0 series 2-1-Forbid-control-characters-in-attributes.patch - Patch for 2.1 series 2-2-Forbid-control-characters-in-attributes.patch - Patch for 2.2 series 3-0-Forbid-control-characters-in-attributes.patch - Patch for 3.0 series

Affected Software

15 affected componentsFixes available
rubygems/rack>=3.0.0.0<3.0.4.1
3.0.4.1
rubygems/rack>=2.2.0.0<2.2.6.1
2.2.6.1
rubygems/rack>=2.1.0.0<2.1.4.2
2.1.4.2
rubygems/rack>=2.0.0<2.0.9.2
2.0.9.2
redhat/rubygem-rack<2.0.9.2
2.0.9.2
redhat/rubygem-rack<2.1.4.2
2.1.4.2
redhat/rubygem-rack<2.2.6.1
2.2.6.1
redhat/rubygem-rack<3.0.4.1
3.0.4.1
Rack Project Rack Ruby<2.0.9.2
Rack Project Rack Ruby>=2.1.0<2.1.4.2
Rack Project Rack Ruby>=2.2.0<2.2.4.1
Rack Rack Ruby<2.0.9.2
Rack Rack Ruby>=2.1.0<2.1.4.2
Rack Rack Ruby>=2.2.0<2.2.4.1
debian/ruby-rack
2.1.4-3+deb11u22.1.4-3+deb11u32.2.6.4-1+deb12u12.2.13-1~deb12u13.1.12-1

Event History

Jan 18, 2023
Advisory Published
06:19 PM
Jan 26, 2023
Data Sourced
via Red Hat·09:52 AM
DescriptionSeverityAffected Software
Feb 9, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Sep 26, 2024
Data Sourced
via Launchpad·07:08 AM
Description
Sep 30, 2024
Data Sourced
via Ubuntu·07:08 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this vulnerability?

The vulnerability ID for this vulnerability is CVE-2022-44572.

2

What is the severity of CVE-2022-44572?

The severity of CVE-2022-44572 is high (7.5).

3

Which versions of Rack are affected by CVE-2022-44572?

Versions >= 2.0.0 of Rack are affected by CVE-2022-44572.

4

How can I fix CVE-2022-44572?

To fix CVE-2022-44572, update to one of the fixed versions: 2.0.9.2, 2.1.4.2, 2.2.6.1, or 3.0.0.1.

5

Where can I find more information about CVE-2022-44572?

You can find more information about CVE-2022-44572 on the following websites: [HackerOne](https://hackerone.com/reports/1639882), [Debian Security Advisory](https://www.debian.org/security/2023/dsa-5530), [GitHub Commit](https://github.com/rack/rack/commit/dc50f8e495f67eb933b1fc33ebee550908d945e6).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203