CRLF Injection Affecting gitlab-rails-ee-fips-17.3 package, versions <17.3.7-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about CRLF Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-GITLABRAILSEEFIPS173-8722256
  • published14 Feb 2025
  • disclosed12 Feb 2025

Introduced: 12 Feb 2025

NewCVE-2025-25184  (opens in a new tab)
CWE-93  (opens in a new tab)
CWE-117  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ee-fips-17.3 to version 17.3.7-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-rails-ee-fips-17.3 package and not the gitlab-rails-ee-fips-17.3 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Scores

version 3.1