rack
Affected
- introduced
0, fixed2.2.19(ecosystem)
Fixed versions
2.2.19
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-61770
Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
Summary
Rack::Multipart::Parser buffers the entire multipart preamble (bytes before the first boundary) in memory without any size limit. A client can send a large preamble followed by a valid boundary, causing significant memory use and potential process termination due to out-of-memory (OOM) conditions.
Details
While searching for the first boundary, the parser appends incoming data into a shared buffer (@sbuf.concat(content)) and scans for the boundary pattern:
@sbuf.scan_until(@body_regex)
If the boundary is not yet found, the parser continues buffering data indefinitely. There is no trimming or size cap on the preamble, allowing attackers to send arbitrary amounts of data before the first boundary.
Impact
Remote attackers can trigger large transient memory spikes by including a long preamble in multipart/form-data requests. The impact scales with allowed request sizes and concurrency, potentially causing worker crashes or severe slowdown due to garbage collection.
Mitigation
High Basis: The source's own band: HIGH
0, fixed 2.2.19 (ecosystem)2.2.19
The export has no generic command for this ecosystem.
3.1, fixed 3.1.17 (ecosystem)3.1.17
The export has no generic command for this ecosystem.
3.2, fixed 3.2.2 (ecosystem)3.2.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0