CVE-2024-35176VulnerabilityPublished 13 Aug 2024Updated 25 Jun 2026

Red Hat Security Advisory: pcs security update

Affects Red HatSource GCVE Database

Authoritative record:CVE-2024-35176· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.10.1 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.10.1

Exploitation evidence

Disclosed: evidence found.
CVE published 16 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/pcs to 8.10.1.

Affected software

Product	Affected	Fixed in
Red Hatredhat/pcs`pkg:rpm/redhat/pcs`Other threats	Affected >=8.0.0 <8.10.1	Fixed in 8.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated pcs packages that address this vulnerability. Users should apply the security update as described in Red Hat advisory RHSA-2024:5338 and the related article https://access.redhat.com/articles/11258. Applying this update mitigates the vulnerability. No additional mitigation steps are required beyond installing the official fix.

Description

A low severity vulnerability (CVE-2024-35176) affects the pcs packages used for command-line configuration of Pacemaker and Corosync utilities in Red Hat Enterprise Linux 8. The issue involves a denial of service (DoS) caused by the REXML parser when processing XML attributes containing many '<' characters. Red Hat has released an update to address this vulnerability in multiple Red Hat Enterprise Linux 8 variants, including High Availability and Resilient Storage editions across various architectures. No known exploits are reported in the wild. The update is available and should be applied to affected systems.

Impact

The vulnerability allows an attacker to cause a denial of service condition by exploiting the REXML parser's handling of XML attributes with many '<' characters. This could disrupt the pcs command-line configuration system for Pacemaker and Corosync utilities, potentially impacting cluster management operations. The severity is rated low, and no known exploits exist in the wild.

Summary

The pcs packages for Red Hat Enterprise Linux 8 contain a vulnerability identified as CVE-2024-35176, where the REXML XML parser can be forced into a denial of service state by parsing XML with many '<' characters in an attribute value. This vulnerability is rated as low severity by Red Hat Product Security. The issue affects multiple Red Hat Enterprise Linux 8 High Availability and Resilient Storage products across x86_64, aarch64, s390x, and ppc64le architectures. Red Hat has issued a security advisory RHSA-2024:5338 with updated pcs packages to fix this issue.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jun 2026, 22:45 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats