Rack is a modular Ruby web server interface. Prior to version 2.2.18, Rack::QueryParser enforces its params_limit only for parameters separated by &, while still splitting on both & and ;. As a result, attackers could use ; separators to bypass the parameter count limit and submit more parameters than intended. Applications or middleware that directly invoke Rack::QueryParser with its default configuration (no explicit delimiter) could be exposed to increased CPU and memory consumption. This can be abused as a limited denial-of-service vector. This issue has been patched in version 2.2.18.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rack | Rack | * | 2.2.18 (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 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 | * |
| Red Hat Satellite 6.15 for RHEL 8 | RedHat | rubygem-rack-0:2.2.20-1.el8sat | * |
| Red Hat Satellite 6.15 for RHEL 8 | RedHat | rubygem-rack-0:2.2.20-1.el8sat | * |
| Red Hat Satellite 6.16 for RHEL 8 | RedHat | rubygem-rack-0:2.2.20-1.el8sat | * |
| Red Hat Satellite 6.16 for RHEL 8 | RedHat | rubygem-rack-0:2.2.20-1.el8sat | * |
| Red Hat Satellite 6.16 for RHEL 9 | RedHat | rubygem-rack-0:2.2.20-1.el9sat | * |
| Red Hat Satellite 6.16 for RHEL 9 | RedHat | rubygem-rack-0:2.2.20-1.el9sat | * |
| Red Hat Satellite 6.17 for RHEL 9 | RedHat | rubygem-rack-0:2.2.20-1.el9sat | * |
| Red Hat Satellite 6.17 for RHEL 9 | RedHat | rubygem-rack-0:2.2.20-1.el9sat | * |
| Ruby-rack | Ubuntu | noble | * |
| Ruby-rack | Ubuntu | plucky | * |
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.