ManageIQ / ManageIQ/linux_admin
CVE-2025-61771 (High) detected in rack-3.1.16.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 30
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
## CVE-2025-61771 - High Severity Vulnerability
Vulnerable Library - rack-3.1.16.gem
Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
Library home page: https://rubygems.org/gems/rack-3.1.16.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-3.1.16.gem
Dependency Hierarchy:
- manageiq-style-1.3.3.gem (Root Library)
- rubocop-rails-2.32.0.gem
- :x: **rack-3.1.16.gem** (Vulnerable Library)
Found in base branch: master
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"stores non-file form fields (parts without a"filename") entirely in memory as Ruby "String"objects. A single large text field in a multipart/form-data request (hundreds of megabytes or more) can consume equivalent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can send large non-file fields to trigger excessive memory usage. Impact scales with request size and concurrency, potentially leading to worker crashes or severe garbage-collection overhead. All Rack applications processing multipart form submissions are affected. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a reasonable size cap for non-file fields (e.g., 2 MiB). Workarounds include restricting maximum request body size at the web-server or proxy layer (e.g., Nginx"client_max_body_size`) and validating and rejecting unusually large form fields at the application level.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-10-07
URL: CVE-2025-61771
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-w9pc-fmgc-vxvw
Release Date: 2025-10-07
Fix Resolution: rack - 3.2.2,rack - 2.2.19,rack - 3.1.17,https://github.com/rack/rack.git - v2.2.19,https://github.com/rack/rack.git - v3.2.2,https://github.com/rack/rack.git - v3.1.17
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /Gemfile.lock and the cached dependency at /vendor/cache/rack-3.1.16.gem, then review the advisory and its listed fixed Rack versions. Update the dependency to a supported fixed version and refresh the lockfile or cache as needed; done means the project no longer references rack-3.1.16.gem and uses 3.1.17, 3.2.2, or 2.2.19.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100