# CVE-2024-13484: Openshift-gitops-operator-container: namespace isolation break

> Attackers can break namespace isolation to create rogue cluster-wide monitoring rules, impacting the platform monitoring stack.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2025
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-58fx-7v9q-3g56, GO-2025-3427

## What is CVE-2024-13484?

CVE-2024-13484 is a high-severity missing authorization vulnerability in Red Hat OpenShift GitOps 1.14, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2024-13484?

3 open source packages ship an affected version, including github.com/redhat-developer/gitops-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/redhat-developer/gitops-operator` | Go | All versions | None |
| `github.com/redhat-developer/gitops-operator` | Go | All versions | 1.16.2 |
| `github.com/redhat-developer/gitops-operator` | Go | All versions | 1.16.2 |

## How do I fix CVE-2024-13484?

Upgrade github.com/redhat-developer/gitops-operator to 1.16.2 or later.

## Is CVE-2024-13484 being exploited?

There is no known exploitation of CVE-2024-13484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13484 and fix it if it is affected.

What it is: CVE-2024-13484 is a high-severity missing authorization vulnerability in Red Hat OpenShift GitOps 1.14, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13484 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/redhat-developer/gitops-operator (Go): affected all versions; no fix listed
- github.com/redhat-developer/gitops-operator (Go): affected all versions; fixed in 1.16.2
- github.com/redhat-developer/gitops-operator (Go): affected all versions; fixed in 1.16.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13484/ (Markdown: https://insights.sbomify.com/CVE-2024-13484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13484
- OSV: https://osv.dev/vulnerability/CVE-2024-13484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13484/
Summaries are generated and may contain mistakes; the official description above is the record.