Homepage

Resource Exhaustion Affecting gitlab-cfssl-self-sign-scripts-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-GITLABCFSSLSELFSIGNSCRIPTS182-13505468
  • published9 Oct 2025
  • disclosed7 Oct 2025
Report a new vulnerability Found a mistake?

Introduced: 7 Oct 2025

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

How to fix?

Upgrade Minimos:latest gitlab-cfssl-self-sign-scripts-18.2 to version 18.2.8-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-cfssl-self-sign-scripts-18.2 package and not the gitlab-cfssl-self-sign-scripts-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::Parser buffers the entire multipart preamble (bytes before the first boundary) in memory without any size limit. A client can send a large preamble followed by a valid boundary, causing significant memory use and potential process termination due to out-of-memory (OOM) conditions. Remote attackers can trigger large transient memory spikes by including a long preamble in multipart/form-data requests. The impact scales with allowed request sizes and concurrency, potentially causing worker crashes or severe slowdown due to garbage collection. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a preamble size limit (e.g., 16 KiB) or discard preamble data entirely. Workarounds include limiting total request body size at the proxy or web server level and monitoring memory and set per-process limits to prevent OOM conditions.