Argo CD web terminal session doesn't expire
- 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.6.14, 2.7.12, 2.8.1, 2.0.0-20230821201509-e047efa8f951
- 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. All versions of Argo CD starting from version 2.6.0 have a bug where open web terminal sessions do not expire. This bug allows users to send any websocket messages even if the token has already expired. The most straightforward scenario is when a user opens the terminal view and leaves it open for an extended period. This allows the user to view sensitive information even when they should have been logged out already. A patch for this vulnerability has been released in the following Argo CD versions: 2.6.14, 2.7.12 and 2.8.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- argoproj argo-cd
From 2.6.0 · fixed in 2.6.14; From 2.7.0 · fixed in 2.7.12
- github.com/argoproj/argo-cdGo
All versions
- github.com/argoproj/argo-cd/v2Go
From 2.6.0 · fixed in 2.6.14; From 2.7.0 · fixed in 2.7.12; From 2.8.0 · fixed in 2.8.1
- github.com/argoproj/argo-cd/v2Go
From 2.6.0 · fixed in 2.6.14
- github.com/argoproj/argo-cd/v2Go
From 2.7.0 · fixed in 2.7.12
- github.com/argoproj/argo-cd/v2Go
From 2.8.0 · fixed in 2.8.1
- github.com/argoproj/argo-cd/v2Go
From 2.0.0-20230718200744-12a5a7a70d6e · fixed in 2.0.0-20230821201509-e047efa8f951