The Argo CD web terminal session does not handle the revocation of user permissions properly.
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd Go |
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd Go |
all versions| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD has a Web-based terminal that allows users to get a shell inside a running pod, just as they would with kubectl exec. Starting in version 2.6.0, when the administrator enables this function and grants permission to the user `p, role:myrole, exec, create, */*, allow`, even if the user revokes this permission, the user can still perform operations in the container, as long as the user keeps the terminal view open for a long time. Although the token expiration and revocation of the user are fixed, however, the fix does not address the situation of revocation of only user `p, role:myrole, exec, create, */*, allow` permissions, which may still lead to the leakage of sensitive information. A patch for this vulnerability has been released in Argo CD versions 2.11.7, 2.10.16, and 2.9.21.
From the CVE record · GitHub_M
Argo CD's web terminal may continue to allow container operations after a user's exec permission is revoked. This requires an administrator to have enabled the terminal, the user to have been granted exec permission, and the user to keep the terminal view open after that permission is revoked. Continued access may expose sensitive information.
Teams running Argo CD 2.6.0 through versions before 2.9.21, 2.10.0 through versions before 2.10.16, or 2.11.0 through versions before 2.11.7 should check their deployments; the Go package github.com/argoproj/argo-cd has no fixed version listed.