A flaw was found in openshift-gitops-operator-container. The openshift.io/cluster-monitoring label is applied to all namespaces that deploy an ArgoCD CR instance, allowing the namespace to create a rogue PrometheusRule. This issue can have adverse effects on the platform monitoring stack, as the rule is rolled out cluster-wide when the label is applied.
Security readout for executives and security teams
Plain-English summary
CVE-2024-13484 is a namespace isolation flaw in Red Hat OpenShift GitOps. A namespace running an ArgoCD custom resource may receive a monitoring label that lets monitoring rules affect the cluster-wide monitoring stack. This can turn a namespace-level issue into a platform-level risk.
Executive priority
Treat as a high-priority platform security update for OpenShift environments. Prioritize shared or multi-tenant clusters because the flaw can cross namespace boundaries and affect cluster-wide monitoring, even though exploitation requires high privileges.
Technical view
The openshift-gitops-operator-container applies the openshift.io/cluster-monitoring label to namespaces deploying an ArgoCD CR. That can allow creation of a rogue PrometheusRule that is rolled out cluster-wide. Red Hat rates this High, CVSS 8.2, CWE-668, with local access and high privileges required.
Likely exposure
Exposure is most likely in Red Hat OpenShift GitOps 1.14 and 1.15 deployments using the affected listed container packages and versions. Risk is higher where non-platform teams can create ArgoCD CRs or PrometheusRule resources in namespaces.
Exploitation context
The CVSS vector requires local access and high privileges, with no user interaction. The source bundle does not show CISA KEV listing or cite active exploitation. The business risk is disruption or manipulation of platform monitoring behavior across the cluster.
Researcher notes
Key issue is improper exposure of cluster monitoring scope through namespace labeling. Public sources identify Red Hat OpenShift GitOps 1.14 and 1.15 packages as affected and reference related GitHub pull requests. The bundle does not provide exploit evidence or detailed fixed-version mapping beyond errata references.
Mitigation direction
Apply applicable Red Hat updates in RHSA-2025:7753, RHSA-2025:8274, and RHSA-2025:9506.
Follow Red Hat’s CVE guidance for affected OpenShift GitOps 1.14 and 1.15 deployments.
Restrict who can create ArgoCD custom resources in tenant namespaces.
Review permissions for creating PrometheusRule resources in cluster-monitoring-labeled namespaces.
Avoid ad hoc label changes unless aligned with Red Hat guidance.
Validation and detection
Inventory OpenShift clusters running Red Hat OpenShift GitOps 1.14 or 1.15.
Compare installed GitOps operator and container package versions with Red Hat’s affected list.
Identify namespaces with ArgoCD custom resources and openshift.io/cluster-monitoring labels.
Audit PrometheusRule resources in those namespaces for unexpected ownership or purpose.
Confirm the relevant Red Hat errata have been applied.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-668: 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.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
5Timeline events
1ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-668 · source CWE mapping
Exposure of Resource to Wrong Sphere
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.