Denial of Service Vulnerability in Rack Content-Disposition parsing
Published 18 Jan 2023 · Updated 1 Dec 2024
Is your project on an affected rack?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.0.0 <2.0.9.2
- Fixed in
- 2.0.9.2
bundle update --conservative rack # Gemfile: '>= 2.0.9.2'- Affected
- >=2.1.0 <2.1.4.2
- Fixed in
- 2.1.4.2
bundle update --conservative rack # Gemfile: '>= 2.1.4.2'- Affected
- >=2.2.0 <2.2.6.1
- Fixed in
- 2.2.6.1
bundle update --conservative rack # Gemfile: '>= 2.2.6.1'- Affected
- >=3.0.0.0 <3.0.4.1
- Fixed in
- 3.0.4.1
bundle update --conservative rack # Gemfile: '>= 3.0.4.1'Details
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.0.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. 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-Fix-ReDoS-vulnerability-in-multipart-parser - Patch for 2.0 series 2-1-Fix-ReDoS-vulnerability-in-multipart-parser - Patch for 2.1 series 2-2-Fix-ReDoS-vulnerability-in-multipart-parser - Patch for 2.2 series 3-0-Fix-ReDoS-vulnerability-in-multipart-parser - Patch for 3.0 series
Is GHSA-93pm-5p5f-3ghx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected rack, and gives you the command that fixes it.
More advisories for rack
- HighCVE-2026-125111Rack: Multipart parsing allows DoS via unbounded scan buffer growth · 10 Nov 2026
- LowCVE-2026-125108Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass · 10 Nov 2026
- MediumCVE-2026-125109Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835 · 10 Nov 2026
- MediumCVE-2026-125110Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch · 10 Nov 2026
- MediumCVE-2026-34835Rack::Request accepts invalid Host characters, enabling host allowlist bypass · 2 Apr 2026
- MediumCVE-2026-34831Rack has Content-Length mismatch in Rack::Files error responses · 2 Apr 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-44571
- Linkdiscuss.rubyonrails.org/t/cve-2022-44571-possible-denial-of-service-vulnerability-in-rack-content-disposition-parsing/82126
- Packagegithub.com/rack/rack
- Linkgithub.com/rack/rack/releases/tag/v3.0.4.1
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2022-44571.yml
- Linkwww.debian.org/security/2023/dsa-5530
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.