Argo CD login screen allows message spoofing if SSO is enabled
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.15, 2.2.9, 2.3.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A vulnerability was found in Argo CD prior to versions 2.3.4, 2.2.9, and 2.1.15 that allows an attacker to spoof error messages on the login screen when single sign on (SSO) is enabled. In order to exploit this vulnerability, an attacker would have to trick the victim to visit a specially crafted URL which contains the message to be displayed. As far as the research of the Argo CD team concluded, it is not possible to specify any active content (e.g. Javascript) or other HTML fragments (e.g. clickable links) in the spoofed message. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. There are currently no known workarounds.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- argoproj argo-cd
fixed in 2.1.15; From 2.2.0 · fixed in 2.2.9; From 2.3.0 · fixed in 2.3.4
- github.com/argoproj/argo-cdGo
All versions
- github.com/argoproj/argo-cd/v2Go
From 2.0.0 · fixed in 2.1.15; From 2.2.0 · fixed in 2.2.9; From 2.3.0 · fixed in 2.3.4
- github.com/argoproj/argo-cd/v2Go
From 2.3.0 · fixed in 2.3.4
- github.com/argoproj/argo-cd/v2Go
From 2.2.0 · fixed in 2.2.9
- github.com/argoproj/argo-cd/v2Go
From 2.0.0 · fixed in 2.1.15
- github.com/argoproj/argo-cdGo
fixed in 2.1.15