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.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rack | Rack | * | 2.0.9.2 (excluding) |
| Rack | Rack | 2.1.0 (including) | 2.1.4.2 (excluding) |
| Rack | Rack | 2.2.0 (including) | 2.2.4.1 (excluding) |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | rubygem-rack-0:2.2.7-1.el8sat | * |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | rubygem-rack-0:2.2.7-1.el8sat | * |
| Ruby-rack | Ubuntu | esm-apps/focal | * |
| Ruby-rack | Ubuntu | esm-apps/jammy | * |
| Ruby-rack | Ubuntu | focal | * |
| Ruby-rack | Ubuntu | jammy | * |
| Ruby-rack | Ubuntu | kinetic | * |
| Ruby-rack | Ubuntu | trusty | * |
| Ruby-rack | Ubuntu | upstream | * |
| Ruby-rack | Ubuntu | xenial | * |
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.