← Übersicht Argo CD

Argo CD will blindly trust JWT claims if anonymous access is enabled

CVE-2022-29165 · GHSA-r642-gv9p-2wjj · GO-2022-0455

Kritisch · CVSS 10.0 Red Hat: Important Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
18.05.2022
Zuletzt geändert
03.03.2026
EPSS (30 Tage)
2.1 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/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. A critical vulnerability has been discovered in Argo CD starting with version 1.4.0 and prior to versions 2.1.15, 2.2.9, and 2.3.4 which would allow unauthenticated users to impersonate as any Argo CD user or role, including the `admin` user, by sending a specifically crafted JSON Web Token (JWT) along with the request. In order for this vulnerability to be exploited, anonymous access to the Argo CD instance must have been enabled. In a default Argo CD installation, anonymous access is disabled. The vulnerability can be exploited to impersonate as any user or role, including the built-in `admin` account regardless of whether it is enabled or disabled. Also, the attacker does not need an account on the Argo CD instance in order to exploit this. If anonymous access to the instance is enabled, an attacker can escalate their privileges, effectively allowing them to gain the same privileges on the cluster as the Argo CD instance, which is cluster admin in a default installation. This will allow the attacker to create, manipulate and delete any resource on the cluster. They may also exfiltrate data by deploying malicious workloads with elevated privileges, thus bypassing any redaction of sensitive data otherwise enforced by the Argo CD API. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. As a workaround, one may disable anonymous access, but upgrading to a patched version is preferable.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 3 behoben.

Red Hat OpenShift GitOps 1.3 Behoben openshift-gitops-1/applicationset-rhel8, openshift-gitops-1/argocd-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 RHSA-2022:4671, RHSA-2022:4691
Red Hat OpenShift GitOps 1.4 Behoben openshift-gitops-1/applicationset-rhel8, openshift-gitops-1/argocd-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 RHSA-2022:4692
Red Hat OpenShift GitOps 1.5 Behoben openshift-gitops-1/applicationset-rhel8, openshift-gitops-1/argocd-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 RHSA-2022:4690

Betroffene Pakete im beobachteten Stack

CVEargoproj/argo-cdkein Fix bekanntCVE-2022-29165
Gogithub.com/argoproj/argo-cd2.1.15GHSA-r642-gv9p-2wjj
Gogithub.com/argoproj/argo-cdkein Fix bekanntGO-2022-0455
Gogithub.com/argoproj/argo-cd/v22.1.15GHSA-r642-gv9p-2wjj
Gogithub.com/argoproj/argo-cd/v22.3.0 → 2.3.4GHSA-r642-gv9p-2wjj
Gogithub.com/argoproj/argo-cd/v22.2.0 → 2.2.9GHSA-r642-gv9p-2wjj
Gogithub.com/argoproj/argo-cd/v22.1.15, 2.2.0 → 2.2.9, 2.3.0 → 2.3.4GO-2022-0455
NVDargoproj:argo_cd1.4.0 → 2.1.15, 2.2.0 → 2.2.9, 2.3.0 → 2.3.4CVE-2022-29165

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 · ohne 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.