GHSA-h4w9-6x78-8vrj Argo CD's external URLs for Deployments can include JavaScript

• Go github.com/argoproj/argo-cd: >= 1.0.0, < 2.1.16 → fixed in 2.1.16 • Go github.com/argoproj/argo-cd/v2: < 2.1.16 → fixed in 2.1.16 • Go github.com/argoproj/argo-cd/v2: >= 2.2.0, < 2.2.10 → fixed in 2.2.10 • Go github.com/argoproj/argo-cd/v2: >= 2.3.0, < 2.3.5 → fixed in 2.3.5 • Go github.com/argoproj/argo-cd/v2: >= 2.4.0, < 2.4.1 → fixed in 2.4.1

Impact All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to a cross-site scripting (XSS) bug allowing a malicious user to inject a `javascript:` link in the UI. When clicked by a victim user, the script will execute with the victim's permissions (up to and including admin). The script would be capable of doing anything which is possible in the UI or via the API, such as creating, modifying, and deleting Kubernetes resources. Patches A patch for this vulnerability has been released in the following Argo CD versions: • v2.4.1 • v2.3.5 • v2.2.10 • v2.1.16 Workarounds There are no completely-safe workarounds besides upgrading. Mitigations: 1. Avoid clicking external links presented in the UI. Here is an example of an Application node with an external link: The link's title is user-configurable. So even if you hover the link, and the tooltip looks safe, the link might be malicious. The only way to be certain that the link is safe is to inspect the page's source. 2. Carefully limit who has permissions to edit resource manifests (this is configured in RBAC). References • Documentation for the external links feature Credits Disclosed by ADA Logics in a security audit of the Argo project sponsored by CNCF and facilitated by OSTIF. Thanks to Adam Korczynski and David Korczynski for their work on the audit. For more information • Open an issue in the Argo CD issue tracker or discussions • Join us on Slack in channel #argo-cd