CVE-2024-41666 The Argo CD web terminal session does not handle the revocation of user permissions properly.
Argo CD fails to revoke active web terminal sessions when user permissions are removed, allowing continued access to container shells and potential data leakage.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-41666?
CVE-2024-41666 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 24 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
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.
Weakness: CWE-269
Which versions are affected by CVE-2024-41666?
9 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v2 Go | From 2.10.0 | 2.10.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.10.0 | 2.10.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.11.0 | 2.11.7 |
github.com/argoproj/argo-cd/v2 Go | From 2.11.0 | 2.11.7 |
github.com/argoproj/argo-cd/v2 Go | From 2.6.0 | 2.9.21, 2.10.16, 2.11.7 |
github.com/argoproj/argo-cd/v2 Go | From 2.6.0 | 2.9.21 |
3 more packages
github.com/argoproj/argo-cd/v2 Go | From 2.6.0 | 2.9.21 |
argo-cd Bitnami | From 2.6.0 | 2.11.7 |
github.com/argoproj/argo-cd Go | All versions | None |
Products include Argoproj Argo Cd.
How do I fix CVE-2024-41666?
Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.10.16, 2.11.7 or 2.9.21.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-41666 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41666 exists.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
Sources
Also known as BIT-argo-cd-2024-41666, GHSA-v8wx-v5jq-qhhw, GO-2024-3006.