Advisory

GHSA-wpv5-97wm-hp9c

Also known as: CVE-2025-61772

Summary

Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)

Details

Summary

Rack::Multipart::Parser can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (CRLFCRLF). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS).

Details

While reading multipart headers, the parser waits for CRLFCRLF using:

@sbuf.scan_until(/(.*?\r\n)\r\n/m)

If the terminator never appears, it continues appending data (@sbuf.concat(content)) indefinitely. There is no limit on accumulated header bytes, so a single malformed part can consume memory proportional to the request body size.

Impact

Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected.

Mitigation

  • Upgrade to a patched Rack version that caps per-part header size (e.g., 64 KiB).
  • Until then, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx client_max_body_size).

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-10-07 17:28 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

rack

RubyGems · All systems

Affected

  • introduced 0, fixed 2.2.19 (ecosystem)

Fixed versions

2.2.19

Fix

The export has no generic command for this ecosystem.

rack

RubyGems · All systems

Affected

  • introduced 3.1, fixed 3.1.17 (ecosystem)

Fixed versions

3.1.17

Fix

The export has no generic command for this ecosystem.

rack

RubyGems · All systems

Affected

  • introduced 3.2, fixed 3.2.2 (ecosystem)

Fixed versions

3.2.2

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences