Homepage

Resource Exhaustion Affecting gitlab-shell-scripts-compat-18.2 package, versions <18.2.8-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

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 Resource Exhaustion vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-GITLABSHELLSCRIPTSCOMPAT182-13505399
  • published9 Oct 2025
  • disclosed7 Oct 2025
Report a new vulnerability Found a mistake?

Introduced: 7 Oct 2025

NewCVE-2025-61771  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade Minimos:latest gitlab-shell-scripts-compat-18.2 to version 18.2.8-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-shell-scripts-compat-18.2 package and not the gitlab-shell-scripts-compat-18.2 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, ``Rack::Multipart::Parserstores non-file form fields (parts without afilename) entirely in memory as Ruby Stringobjects. A single large text field in a multipart/form-data request (hundreds of megabytes or more) can consume equivalent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can send large non-file fields to trigger excessive memory usage. Impact scales with request size and concurrency, potentially leading to worker crashes or severe garbage-collection overhead. All Rack applications processing multipart form submissions are affected. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a reasonable size cap for non-file fields (e.g., 2 MiB). Workarounds include restricting maximum request body size at the web-server or proxy layer (e.g., Nginxclient_max_body_size`) and validating and rejecting unusually large form fields at the application level.