CVE-2022-31035: External URLs for Deployments can include javascript in argo-cd
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:
!Application node in the Argo CD UI 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
Other sources
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All 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. A patch for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. There are no completely-safe workarounds besides upgrading.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID for the Argo CD vulnerability?
The vulnerability ID for the Argo CD vulnerability is CVE-2022-31035.
What is Argo CD?
Argo CD is a declarative GitOps continuous delivery tool for Kubernetes.
What is the severity of CVE-2022-31035?
The severity of CVE-2022-31035 is critical.
How does the Argo CD vulnerability allow for cross-site scripting (XSS) attacks?
The Argo CD vulnerability allows a malicious user to inject a `javascript:` link in the UI, enabling cross-site scripting attacks.
Which versions of Argo CD are affected by CVE-2022-31035?
All versions of Argo CD starting from v1.0.0 up to and including v2.4.0 are affected by CVE-2022-31035.
How can a malicious user exploit the Argo CD vulnerability?
A malicious user can exploit the Argo CD vulnerability by tricking a victim user into clicking on the injected `javascript:` link in the UI.
What is the fix for the Argo CD vulnerability?
Update to a version of Argo CD that is not affected by CVE-2022-31035, such as v2.4.1 or later.
Are there any references related to the CVE-2022-31035 vulnerability?
Yes, you can find more information about the CVE-2022-31035 vulnerability in the following references: [Link 1](https://argo-cd.readthedocs.io/en/stable/user-guide/external-url/), [Link 2](https://github.com/argoproj/argo-cd/commit/8bc3ef690de29c68a36f473908774346a44d4038), [Link 3](https://github.com/argoproj/argo-cd/security/advisories/GHSA-h4w9-6x78-8vrj).