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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Argo_cd | Argoproj | 1.4.0 (including) | 2.1.15 (excluding) |
Argo_cd | Argoproj | 2.2.0 (including) | 2.2.9 (excluding) |
Argo_cd | Argoproj | 2.3.0 (including) | 2.3.4 (excluding) |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/applicationset-rhel8:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/argocd-rhel8:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/dex-rhel8:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-operator-bundle:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-rhel8:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-rhel8-operator:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/kam-delivery-rhel8:v1.3.10-1 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/applicationset-rhel8:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/argocd-rhel8:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/dex-rhel8:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-operator-bundle:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-rhel8:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/gitops-rhel8-operator:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.3 | RedHat | openshift-gitops-1/kam-delivery-rhel8:v1.3.9-3 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/applicationset-rhel8:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/argocd-rhel8:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/dex-rhel8:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/gitops-operator-bundle:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/gitops-rhel8:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/gitops-rhel8-operator:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.4 | RedHat | openshift-gitops-1/kam-delivery-rhel8:v1.4.7-2 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/applicationset-rhel8:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/argocd-rhel8:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/dex-rhel8:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/gitops-operator-bundle:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/gitops-rhel8:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/gitops-rhel8-operator:v1.5.1-4 | * |
Red Hat OpenShift GitOps 1.5 | RedHat | openshift-gitops-1/kam-delivery-rhel8:v1.5.1-4 | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.