Improper Validation of Specified Quantity in Input Affecting pcs package, versions <0:0.10.8-1.el8_4.8


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.06% (18th 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 IDSNYK-RHEL8-PCS-13866881
  • published10 Nov 2025
  • disclosed7 Oct 2025

Introduced: 7 Oct 2025

CVE-2025-61771  (opens in a new tab)
CWE-1284  (opens in a new tab)

How to fix?

Upgrade RHEL:8 pcs to version 0:0.10.8-1.el8_4.8 or higher.
This issue was patched in RHSA-2025:19948.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcs package and not the pcs package as distributed by RHEL. See How to fix? for RHEL:8 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.

CVSS Base Scores

version 3.1