Description
Vulnerable Library - rack-contrib-2.3.0.gem
Contributed Rack Middleware and Utilities
Library home page: https://rubygems.org/gems/rack-contrib-2.3.0.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-contrib-2.3.0.gem
Vulnerabilities
Vulnerability | Severity | Exploit Maturity | EPSS | Dependency | Type | Fixed in (rack-contrib version) | Remediation Possible** | Reachability | |
---|---|---|---|---|---|---|---|---|---|
CVE-2024-35231 | 8.6 | Not Defined | 0.1% | rack-contrib-2.3.0.gem | Direct | rack-contrib - 2.5.0 | ✅ | ||
CVE-2025-46727 | 7.5 | Not Defined | 0.3% | rack-2.2.11.gem | Transitive | N/A* | ❌ | ||
CVE-2025-27610 | 7.5 | Not Defined | 0.1% | rack-2.2.11.gem | Transitive | N/A* | ❌ | ||
CVE-2025-27111 | 5.3 | Not Defined | 0.2% | rack-2.2.11.gem | Transitive | N/A* | ❌ | ||
CVE-2025-32441 | 4.2 | Not Defined | 0.0% | rack-2.2.11.gem | Transitive | N/A* | ❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-35231
Vulnerable Library - rack-contrib-2.3.0.gem
Contributed Rack Middleware and Utilities
Library home page: https://rubygems.org/gems/rack-contrib-2.3.0.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-contrib-2.3.0.gem
Dependency Hierarchy:
- ❌ rack-contrib-2.3.0.gem (Vulnerable Library)
Found in base branch: master
Vulnerability Details
rack-contrib provides contributed rack middleware and utilities for Rack, a Ruby web server interface. Versions of rack-contrib prior to 2.5.0 are vulnerable to denial of service due to the fact that the user controlled data profiler_runs
was not constrained to any limitation. This would lead to allocating resources on the server side with no limitation and a potential denial of service by remotely user-controlled data. Version 2.5.0 contains a patch for the issue.
Publish Date: 2024-05-27
URL: CVE-2024-35231
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.1%
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-8c8q-2xw3-j869
Release Date: 2024-05-27
Fix Resolution: rack-contrib - 2.5.0
In order to enable automatic remediation, please create workflow rules
CVE-2025-46727
Vulnerable Library - rack-2.2.11.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-2.2.11.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-2.2.11.gem
Dependency Hierarchy:
- rack-contrib-2.3.0.gem (Root Library)
- ❌ rack-2.2.11.gem (Vulnerable Library)
Found in base branch: master
Vulnerability Details
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-05-07
URL: CVE-2025-46727
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.3%
CVSS 3 Score Details (7.5)
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
Suggested Fix
Type: Upgrade version
Release Date: 2025-05-07
Fix Resolution: https://github.com/rack/rack.git - v3.0.16
CVE-2025-27610
Vulnerable Library - rack-2.2.11.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-2.2.11.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-2.2.11.gem
Dependency Hierarchy:
- rack-contrib-2.3.0.gem (Root Library)
- ❌ rack-2.2.11.gem (Vulnerable Library)
Found in base branch: master
Vulnerability Details
Rack provides an interface for developing web applications in Ruby. Prior to versions 2.2.13, 3.0.14, and 3.1.12, "Rack::Static" can serve files under the specified "root:" even if "urls:" are provided, which may expose other files under the specified "root:" unexpectedly. The vulnerability occurs because "Rack::Static" does not properly sanitize user-supplied paths before serving files. Specifically, encoded path traversal sequences are not correctly validated, allowing attackers to access files outside the designated static file directory. By exploiting this vulnerability, an attacker can gain access to all files under the specified "root:" directory, provided they are able to determine then path of the file. Versions 2.2.13, 3.0.14, and 3.1.12 contain a patch for the issue. Other mitigations include removing usage of "Rack::Static", or ensuring that "root:" points at a directory path which only contains files which should be accessed publicly. It is likely that a CDN or similar static file server would also mitigate the issue.
Publish Date: 2025-03-10
URL: CVE-2025-27610
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.1%
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
CVE-2025-27111
Vulnerable Library - rack-2.2.11.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-2.2.11.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-2.2.11.gem
Dependency Hierarchy:
- rack-contrib-2.3.0.gem (Root Library)
- ❌ rack-2.2.11.gem (Vulnerable Library)
Found in base branch: master
Vulnerability Details
Rack is a modular Ruby web server interface. The Rack::Sendfile middleware logs unsanitised header values from the X-Sendfile-Type header. An attacker can exploit this by injecting escape sequences (such as newline characters) into the header, resulting in log injection. This vulnerability is fixed in 2.2.12, 3.0.13, and 3.1.11.
Publish Date: 2025-03-04
URL: CVE-2025-27111
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.2%
CVSS 3 Score Details (5.3)
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: Low
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Origin: GHSA-8cgq-6mh2-7j6v
Release Date: 2025-03-04
Fix Resolution: 3.1.11
CVE-2025-32441
Vulnerable Library - rack-2.2.11.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-2.2.11.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/rack-2.2.11.gem
Dependency Hierarchy:
- rack-contrib-2.3.0.gem (Root Library)
- ❌ rack-2.2.11.gem (Vulnerable Library)
Found in base branch: master
Vulnerability Details
Rack is a modular Ruby web server interface. Prior to version 2.2.14, when using the "Rack::Session::Pool" middleware, simultaneous rack requests can restore a deleted rack session, which allows the unauthenticated user to occupy that session. Rack session middleware prepares the session at the beginning of request, then saves is back to the store with possible changes applied by host rack application. This way the session becomes to be a subject of race conditions in general sense over concurrent rack requests. When using the "Rack::Session::Pool" middleware, and provided the attacker can acquire a session cookie (already a major issue), the session may be restored if the attacker can trigger a long running request (within that same session) adjacent to the user logging out, in order to retain illicit access even after a user has attempted to logout. Version 2.2.14 contains a patch for the issue. Some other mitigations are available. Either ensure the application invalidates sessions atomically by marking them as logged out e.g., using a "logged_out" flag, instead of deleting them, and check this flag on every request to prevent reuse; or implement a custom session store that tracks session invalidation timestamps and refuses to accept session data if the session was invalidated after the request began.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-05-07
URL: CVE-2025-32441
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (4.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Release Date: 2025-05-07
Fix Resolution: https://github.com/rack/rack.git - v2.2.14
In order to enable automatic remediation for this issue, please create workflow rules