FKIE_CVE-2025-61770

Vulnerability from fkie_nvd - Published: 2025-10-07 15:16 - Updated: 2026-10-19 16:10
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
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.
References
security-advisories@github.comhttps://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181ePatch
security-advisories@github.comhttps://github.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29ePatch
security-advisories@github.comhttps://github.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fdPatch
security-advisories@github.comhttps://github.com/rack/rack/security/advisories/GHSA-p543-xpfm-54cpMitigation, Vendor Advisory
Impacted products
Vendor Product Version
rack rack *
rack rack *
rack rack *
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "rack",
          "vendor": "rack",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 2.2.19"
            },
            {
              "status": "affected",
              "version": "\u003e= 3.1, \u003c 3.1.17"
            },
            {
              "status": "affected",
              "version": "\u003e= 3.2, \u003c 3.2.2"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:*",
              "matchCriteriaId": "EBB6060B-A06F-4A88-8457-AD850E63E562",
              "versionEndExcluding": "2.2.19",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:*",
              "matchCriteriaId": "850EC79C-0F31-441F-9001-B7CA0CD7758F",
              "versionEndExcluding": "3.1.17",
              "versionStartIncluding": "3.1.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:*",
              "matchCriteriaId": "9A009CC5-8010-446E-A12B-BF5314CA5BEB",
              "versionEndExcluding": "3.2.2",
              "versionStartIncluding": "3.2.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "Rack es una interfaz modular de servidor web Ruby. En versiones anteriores a 2.2.19, 3.1.17 y 3.2.2, \u0027Rack::Multipart::Parser\u0027 almacena en b\u00fafer el pre\u00e1mbulo multipart completo (bytes antes del primer l\u00edmite) en memoria sin ning\u00fan l\u00edmite de tama\u00f1o. Un cliente puede enviar un pre\u00e1mbulo grande seguido de un l\u00edmite v\u00e1lido, causando un uso significativo de memoria y una posible terminaci\u00f3n del proceso debido a condiciones de falta de memoria (OOM). Atacantes remotos pueden desencadenar grandes picos transitorios de memoria al incluir un pre\u00e1mbulo largo en solicitudes multipart/form-data. El impacto escala con los tama\u00f1os de solicitud permitidos y la concurrencia, causando potencialmente ca\u00eddas de workers o una desaceleraci\u00f3n severa debido a la recolecci\u00f3n de basura. Las versiones 2.2.19, 3.1.17 y 3.2.2 imponen un l\u00edmite de tama\u00f1o de pre\u00e1mbulo (p. ej., 16 KiB) o descartan los datos del pre\u00e1mbulo por completo. Las soluciones incluyen limitar el tama\u00f1o total del cuerpo de la solicitud a nivel de proxy o servidor web y monitorear la memoria y establecer l\u00edmites por proceso para prevenir condiciones OOM."
    }
  ],
  "id": "CVE-2025-61770",
  "lastModified": "2026-10-19T16:10:00.260",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-61770",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-10-07T15:23:07.044511Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-10-07T15:16:02.950",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29e"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fd"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Mitigation",
        "Vendor Advisory"
      ],
      "url": "https://github.com/rack/rack/security/advisories/GHSA-p543-xpfm-54cp"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-400"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.