Argo CD web terminal session doesn't expire
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
2.0.0-20230821201509-e047efa8f951| github.com/argoproj/argo-cd Go |
| No fix yet |
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.
From the CVE record · GitHub_M
Open Argo CD web terminal sessions do not expire when the user's token expires. A user who opened a terminal and leaves it open can continue sending WebSocket messages and viewing sensitive information after they should have been logged out.
Teams running Argo CD 2.6.0 or later should check affected releases before 2.6.14, 2.7.12, or 2.8.1, as well as users of the affected Go packages github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd.