Bug 2364966 (CVE-2025-46727) - CVE-2025-46727 rubygem-rack: Unbounded-Parameter DoS in Rack::QueryParser
Summary: CVE-2025-46727 rubygem-rack: Unbounded-Parameter DoS in Rack::QueryParser
Keywords:
Status: NEW
Alias: CVE-2025-46727
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2364996 2364997 2364998 2364999 2365000
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-08 00:01 UTC by OSIDB Bzimport
Modified: 2025-05-14 14:12 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:7604 0 None None None 2025-05-14 14:12:14 UTC
Red Hat Product Errata RHSA-2025:7605 0 None None None 2025-05-14 14:12:31 UTC

Description OSIDB Bzimport 2025-05-08 00:01:08 UTC
Rack is a modular Ruby web server interface. Prior to versions 2.2.14, 3.0.16, and 3.1.14, `Rack::QueryParser` parses query strings and `application/x-www-form-urlencoded` bodies into Ruby data structures without imposing any limit on the number of parameters, allowing attackers to send requests with extremely large numbers of parameters. The vulnerability arises because `Rack::QueryParser` iterates over each `&`-separated key-value pair and adds it to a Hash without enforcing an upper bound on the total number of parameters. This allows an attacker to send a single request containing hundreds of thousands (or more) of parameters, which consumes excessive memory and CPU during parsing. An attacker can trigger denial of service by sending specifically crafted HTTP requests, which can cause memory exhaustion or pin CPU resources, stalling or crashing the Rack server. This results in full service disruption until the affected worker is restarted. Versions 2.2.14, 3.0.16, and 3.1.14 fix the issue. Some other mitigations are available. One may use middleware to enforce a maximum query string size or parameter count, or employ a reverse proxy (such as Nginx) to limit request sizes and reject oversized query strings or bodies. Limiting request body sizes and query string lengths at the web server or CDN level is an effective mitigation.

Comment 3 errata-xmlrpc 2025-05-14 14:12:12 UTC
This issue has been addressed in the following products:

  Red Hat Satellite 6.17 for RHEL 9

Via RHSA-2025:7604 https://access.redhat.com/errata/RHSA-2025:7604

Comment 4 errata-xmlrpc 2025-05-14 14:12:29 UTC
This issue has been addressed in the following products:

  Red Hat Satellite 6.16 for RHEL 8
  Red Hat Satellite 6.16 for RHEL 9

Via RHSA-2025:7605 https://access.redhat.com/errata/RHSA-2025:7605


Note You need to log in before you can comment on or make changes to this bug.