solid_cache-1.0.7.gem: 4 vulnerabilities (highest severity is: 7.5)

[mend-for-github-com]

Vulnerable Library - solid_cache-1.0.7.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-session-2.1.0.gem

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (solid_cache version)	Remediation Possible**
CVE-2025-49007	High	7.5	rack-3.1.12.gem	Transitive	N/A*	❌
CVE-2025-46727	High	7.5	rack-3.1.12.gem	Transitive	N/A*	❌
CVE-2025-46336	Medium	4.2	rack-session-2.1.0.gem	Transitive	N/A*	❌
CVE-2025-32441	Medium	4.2	rack-session-2.1.0.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-2025-49007

Vulnerable Library - rack-3.1.12.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.12.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-3.1.12.gem

Dependency Hierarchy:

• solid_cache-1.0.7.gem (Root Library)
  • railties-8.0.2.gem
    • rackup-2.2.1.gem
      • ❌ rack-3.1.12.gem (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Rack is a modular Ruby web server interface. Starting in version 3.1.0 and prior to version 3.1.16, there is a denial of service vulnerability in the Content-Disposition parsing component of Rack. This is very similar to the previous security issue CVE-2022-44571. Carefully crafted input can cause Content-Disposition header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. This header is used typically used in multipart parsing. Any applications that parse multipart posts using Rack (virtually all Rails applications) are impacted. Version 3.1.16 contains a patch for the vulnerability.

Publish Date: 2025-06-04

URL: CVE-2025-49007

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-47m2-26rw-j2jw

Release Date: 2025-06-04

Fix Resolution: rack - 3.1.16

CVE-2025-46727

Vulnerable Library - rack-3.1.12.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.12.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-3.1.12.gem

Dependency Hierarchy:

• solid_cache-1.0.7.gem (Root Library)
  • railties-8.0.2.gem
    • rackup-2.2.1.gem
      • ❌ rack-3.1.12.gem (Vulnerable Library)

Found in base branch: main

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.

Publish Date: 2025-05-07

URL: CVE-2025-46727

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2025-05-07

Fix Resolution: https://github.com/rack/rack.git - v2.2.14

CVE-2025-46336

Vulnerable Library - rack-session-2.1.0.gem

Library home page: https://rubygems.org/gems/rack-session-2.1.0.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-session-2.1.0.gem

Dependency Hierarchy:

• solid_cache-1.0.7.gem (Root Library)
  • railties-8.0.2.gem
    • actionpack-8.0.2.gem
      • ❌ rack-session-2.1.0.gem (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Rack::Session is a session management implementation for Rack. In versions starting from 2.0.0 to before 2.1.1, 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. This issue has been patched in version 2.1.1.

Publish Date: 2025-05-08

URL: CVE-2025-46336

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-9j94-67jr-4cqj

Release Date: 2025-05-08

Fix Resolution: rack-session - 2.1.1

CVE-2025-32441

Vulnerable Library - rack-session-2.1.0.gem

Library home page: https://rubygems.org/gems/rack-session-2.1.0.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-session-2.1.0.gem

Dependency Hierarchy:

• solid_cache-1.0.7.gem (Root Library)
  • railties-8.0.2.gem
    • actionpack-8.0.2.gem
      • ❌ rack-session-2.1.0.gem (Vulnerable Library)

Found in base branch: main

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.

Publish Date: 2025-05-07

URL: CVE-2025-32441

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-9j94-67jr-4cqj

Release Date: 2025-05-07

Fix Resolution: rack-session - 2.1.1