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

Open Beginner friendly
#57 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with /Gemfile.lock and inspect the rack-test-2.1.0 to rack-2.2.9 dependency path described in the issue. Update the resolved Rack version to a listed fixed release, then verify the lockfile no longer selects 2.2.9 and the project checks pass.

Written by the indexing model from the issue text.

Description

Mend: dependency security vulnerability stale

CVE-2025-25184 - 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)
    • ❌ rack-2.2.9.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.11, 3.0.12, and 3.1.10, Rack::CommonLogger can be exploited by crafting input that includes newline characters to manipulate log entries. The supplied proof-of-concept demonstrates injecting malicious content into logs. When a user provides the authorization credentials via Rack::Auth::Basic, if success, the username will be put in env['REMOTE_USER'] and later be used by Rack::CommonLogger for logging purposes. The issue occurs when a server intentionally or unintentionally allows a user creation with the username contain CRLF and white space characters, or the server just want to log every login attempts. If an attacker enters a username with CRLF character, the logger will log the malicious username with CRLF characters into the logfile. Attackers can break log formats or insert fraudulent entries, potentially obscuring real activity or injecting malicious data into log files. Versions 2.2.11, 3.0.12, and 3.1.10 contain a fix.

Publish Date: 2025-02-12

URL: CVE-2025-25184

CVSS 3 Score Details (6.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: High
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/rack/rack/security/advisories/GHSA-7g2v-jj9q-g3rg

Release Date: 2025-02-12

Fix Resolution: rack - 2.2.11,3.0.12,3.1.11

Step up your Open Source Security Game with Mend here

Dominant language
Ruby
Stars
1
Forks
12
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ManageIQ/dbus_api_service

All issues in ManageIQ/dbus_api_service

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.