Security readout for executives and security teams
Plain-English summary
CVE-2019-10153 can make cluster recovery fail when fence-agents handles guest VM metadata containing non-ASCII characters. The business risk is operational disruption: automated recovery or fencing may not work correctly for affected clustered systems, increasing downtime during failures.
Executive priority
Treat this as a moderate operational resilience issue. It is not presented as data theft or code execution, but affected clusters may fail to recover automatically during incidents, which can extend outages.
Technical view
In ClusterLabs fence-agents before 4.3.4, fence_rhevm can exit with an exception when processing non-ASCII characters in a guest VM comment or related fields. In cluster environments, that exception can deny service by preventing automated recovery for a VM participating in the cluster.
Likely exposure
Exposure is most likely where ClusterLabs fence-agents before 4.3.4 is deployed and fence_rhevm is used for cluster fencing or recovery workflows involving guest VM metadata.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The trigger requires influence over VM fields such as comments or other metadata, and the impact described is availability loss in cluster recovery.
Researcher notes
The weakness is tied to character handling, classified as CWE-172. Public details identify the affected component and fixed version, but the bundle does not provide enough evidence to assess exploit prevalence beyond the documented denial-of-service condition.
Mitigation direction
- Upgrade fence-agents to version 4.3.4 or a vendor-fixed package.
- Apply Red Hat guidance where RHSA-2019:2037 is applicable.
- Identify clusters using fence_rhevm and prioritize those systems.
- If upgrade is delayed, review vendor guidance for temporary operational controls.
- Avoid relying on metadata workarounds as a permanent fix.
Validation and detection
- Check installed fence-agents versions across cluster nodes.
- Confirm whether fence_rhevm is configured in cluster fencing workflows.
- Review vendor advisories for package names and fixed builds.
- Verify cluster recovery behavior after applying the fixed package.
- Document any remaining unsupported or unpatched cluster nodes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-172: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-10153 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L3.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10153CVE reference · x_refsource_CONFIRM
- https://github.com/ClusterLabs/fence-agents/pull/255CVE reference · x_refsource_CONFIRM
- https://github.com/ClusterLabs/fence-agents/pull/272CVE reference · x_refsource_CONFIRM
- RHSA-2019:2037CVE reference · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Encoding Error
Encoding Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.