Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v3 Go |
|
|
| github.com/argoproj/argo-cd/v2 Go |
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v3 Go |
|
|
| github.com/argoproj/argo-cd/v2 Go |
≤ 2.14.21all versions| No fix yet |
| github.com/argoproj/argo-cd Go |
| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Prior to 3.2.12, 3.3.10, and 3.4.2, Argo CD users with application write access can set link.argocd.argoproj.io/* annotations whose pipe-separated values are rendered by ui/src/app/applications/components/application-summary/application-summary.tsx in the Summary tab URLs section as anchor href values without URL validation, allowing javascript: execution in a higher-privileged user's authenticated Argo CD origin session. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.
From the CVE record · GitHub_M
Argo CD renders application link annotations as URLs without validating them. A user with application write access can set a malicious link that executes JavaScript in a higher-privileged user's authenticated Argo CD session when that user views the application's Summary tab.
Teams running Argo CD v3 before 3.2.12, 3.3.0-rc1 through before 3.3.10, or 3.4.0-rc1 through before 3.4.2 should check their deployments; the listed v2 and older Go packages are also affected and have no fix in those lines.