CVE-2024-13484 is a high-severity (CVSS 8.2) CWE-668 vulnerability in github.com/redhat-developer/gitops-operator. A fix is available for github.com/redhat-developer/gitops-operator — see the affected versions and patch details below.
Openshift-gitops-operator-container: namespace isolation break
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-13484.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/redhat-developer/gitops-operatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/redhat-developer/gitops-operator | all versions | 1.16.2go get github.com/redhat-developer/gitops-operator@v1.16.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/redhat-developer/gitops-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/redhat-developer/gitops-operator to 1.16.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-13484 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
To exploit this flaw, a local attacker must be logged into the system with admin privileges, limiting the possibility of this issue to be exploited. For this reason, this flaw has been rated with a Moderate severity.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-13484 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift GitOps 1.14 | openshift-gitops-1/argocd-rhel8:v1.14.4-1 | RHSA-2025:8274 |
| Red Hat OpenShift GitOps 1.15 | openshift-gitops-1/argocd-extensions-rhel8:v1.15.2-4 | RHSA-2025:7753 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/gitops-rhel8-operator:1.16 | RHSA-2025:9506 |
Frequently Asked Questions
Is CVE-2024-13484 in your dependencies?
Find it across Go, including transitive dependencies.