ManageIQ / ManageIQ/dbus_api_service

CVE-2025-32441 (Medium) detected in rack-2.2.9.gem

Open Beginner friendly
#60 2 comments 0 reactions 0 assignees View on GitHub
Mend: dependency security vulnerability stale
Dominant language
Ruby
Stars
1
Forks
12
PR merge metrics
No merged PRs in 30d

Description

## CVE-2025-32441 - Medium Severity Vulnerability
Vulnerable Library - rack-2.2.9.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.9.gem


Path to dependency file: /Gemfile.lock


Path to vulnerable library: /home/wss-scanner/.gem/ruby/3.2.0/cache/rack-2.2.9.gem


Dependency Hierarchy:
- rack-test-2.1.0.gem (Root Library)
- :x: **rack-2.2.9.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



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


Release Date: 2025-05-07


Fix Resolution: https://github.com/rack/rack-session.git - v2.1.1,https://github.com/rack/rack.git - v2.2.14,rack-session - 2.1.1

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Contributor guide

Open the contributing guide

Research direction

Start with /Gemfile.lock and the rack-test-2.1.0 dependency hierarchy. Check the resolved Rack version against CVE-2025-32441 and update the dependency to the stated fixed version; done means the lockfile no longer resolves rack-2.2.9.gem and the vulnerability scan is clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend, security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.