Argo CD users with any cluster secret update access may update out-of-bounds cluster secrets
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
|
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
|
|
2.6.2| github.com/argoproj/argo-cd/v2 Go |
|
|
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All Argo CD versions starting with 2.3.0-rc1 and prior to 2.3.17, 2.4.23 2.5.11, and 2.6.2 are vulnerable to an improper authorization bug which allows users who have the ability to update at least one cluster secret to update any cluster secret. The attacker could use this access to escalate privileges (potentially controlling Kubernetes resources) or to break Argo CD functionality (by preventing connections to external clusters). A patch for this vulnerability has been released in Argo CD versions 2.6.2, 2.5.11, 2.4.23, and 2.3.17. Two workarounds are available. Either modify the RBAC configuration to completely revoke all `clusters, update` access, or use the `destinations` and `clusterResourceWhitelist` fields to apply similar restrictions as the `namespaces` and `clusterResources` fields.
From the CVE record · GitHub_M
Argo CD has an improper authorization bug in cluster secret updates. A user who can update at least one cluster secret can update any cluster secret, potentially escalating privileges or disrupting connections to external clusters.
Teams running Argo CD from 2.3.0-rc1 up to, but not including, 2.3.17, 2.4.23, 2.5.11, or 2.6.2 in their respective release lines should check their deployments.