Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, 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. 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. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a preamble size limit (e.g., 16 KiB) or discard preamble data entirely. Workarounds include limiting total request body size at the proxy or web server level and monitoring memory and set per-process limits to prevent OOM conditions.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rack | Rack | * | 2.2.19 (excluding) |
| Rack | Rack | 3.1.0 (including) | 3.1.17 (excluding) |
| Rack | Rack | 3.2.0 (including) | 3.2.2 (excluding) |
| Red Hat Enterprise Linux 10 | RedHat | pcs-0:0.12.0-3.el10_0.3 | * |
| Red Hat Enterprise Linux 10 | RedHat | pcs-0:0.12.1-1.el10_1.1 | * |
| Red Hat Enterprise Linux 7 Extended Lifecycle Support | RedHat | pcs-0:0.9.169-3.el7_9.5 | * |
| Red Hat Enterprise Linux 8 | RedHat | pcs-0:0.10.18-2.el8_10.7 | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | pcs-0:0.10.8-1.el8_4.8 | * |
| Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On | RedHat | pcs-0:0.10.8-1.el8_4.8 | * |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | RedHat | pcs-0:0.10.12-6.el8_6.10 | * |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | RedHat | pcs-0:0.10.12-6.el8_6.10 | * |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | RedHat | pcs-0:0.10.15-4.el8_8.9 | * |
| Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | RedHat | pcs-0:0.10.15-4.el8_8.9 | * |
| Red Hat Enterprise Linux 9 | RedHat | pcs-0:0.11.9-2.el9_6.2 | * |
| Red Hat Enterprise Linux 9 | RedHat | pcs-0:0.11.10-1.el9_7.1 | * |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | RedHat | pcs-0:0.11.1-10.el9_0.9 | * |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | RedHat | pcs-0:0.11.4-7.el9_2.6 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | pcs-0:0.11.7-2.el9_4.5 | * |
| Ruby-rack | Ubuntu | esm-apps/bionic | * |
| Ruby-rack | Ubuntu | esm-apps/focal | * |
| Ruby-rack | Ubuntu | esm-apps/jammy | * |
| Ruby-rack | Ubuntu | esm-apps/xenial | * |
| Ruby-rack | Ubuntu | esm-infra-legacy/trusty | * |
| Ruby-rack | Ubuntu | jammy | * |
| Ruby-rack | Ubuntu | noble | * |
| Ruby-rack | Ubuntu | plucky | * |
| Ruby-rack | Ubuntu | questing | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html