← Übersicht Argo CD

argo-cd Controller reconciles apps outside configured namespaces when sharding is enabled

CVE-2023-22736 · GHSA-6p4m-hw2h-6gmw · GO-2023-1512

Hoch · CVSS 8.5 Red Hat: Important Netzwerk · mit Login Fix verfügbar

Veröffentlicht
25.01.2023
Zuletzt geändert
10.09.2026
EPSS (30 Tage)
0.8 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions starting with 2.5.0-rc1 and above, prior to 2.5.8, and version 2.6.0-rc4, are vulnerable to an authorization bypass bug which allows a malicious Argo CD user to deploy Applications outside the configured allowed namespaces. Reconciled Application namespaces are specified as a comma-delimited list of glob patterns. When sharding is enabled on the Application controller, it does not enforce that list of patterns when reconciling Applications. For example, if Application namespaces are configured to be argocd-*, the Application controller may reconcile an Application installed in a namespace called other, even though it does not start with argocd-. Reconciliation of the out-of-bounds Application is only triggered when the Application is updated, so the attacker must be able to cause an update operation on the Application resource. This bug only applies to users who have explicitly enabled the "apps-in-any-namespace" feature by setting `application.namespaces` in the argocd-cmd-params-cm ConfigMap or otherwise setting the `--application-namespaces` flags on the Application controller and API server components. The apps-in-any-namespace feature is in beta as of this Security Advisory's publish date. The bug is also limited to Argo CD instances where sharding is enabled by increasing the `replicas` count for the Application controller. Finally, the AppProjects' `sourceNamespaces` field acts as a secondary check against this exploit. To cause reconciliation of an Application in an out-of-bounds namespace, an AppProject must be available which permits Applications in the out-of-bounds namespace. A patch for this vulnerability has been released in versions 2.5.8 and 2.6.0-rc5. As a workaround, running only one replica of the Application controller will prevent exploitation of this bug. Making sure all AppProjects' sourceNamespaces are restricted within the confines of the configured Application namespaces will also prevent exploitation of this bug.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 1 behoben, 1 nicht betroffen.

Red Hat OpenShift GitOps 1.7 Behoben openshift-gitops-1/argocd-rhel8 RHSA-2023:0467
Nicht betroffen (1)
Red Hat OpenShift GitOps 1.7Nicht betroffenverwundbarer Code nicht enthaltenopenshift-gitops-1/console-plugin-rhel8, openshift-gitops-1/dex-rhel8, openshift-gitops-1/gitops-operator-bundle, openshift-gitops-1/gitops-rhel8, openshift-gitops-1/gitops-rhel8-operator, openshift-gitops-1/kam-delivery-rhel8

Betroffene Pakete im beobachteten Stack

CVEargoproj/argo-cdkein Fix bekanntCVE-2023-22736
Gogithub.com/argoproj/argo-cdkein Fix bekanntGO-2023-1512
Gogithub.com/argoproj/argo-cd/v22.5.0-rc1 → 2.5.8GHSA-6p4m-hw2h-6gmw
Gogithub.com/argoproj/argo-cd/v22.6.0-rc4 → 2.6.0-rc5GHSA-6p4m-hw2h-6gmw
Gogithub.com/argoproj/argo-cd/v22.5.0-rc1 → 2.5.8, 2.6.0-rc4 → 2.6.0-rc5GO-2023-1512
NVDargoproj:argo_cd2.5.0 → 2.5.8CVE-2023-22736

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.