Privilege Escalation in github.com/argoproj/argo-cd/v2 (CVE-2024-41666)
Summary
Vulnerability in github.com/argoproj/argo-cd/v2 (CVE-2024-41666). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.9.21, 2.10.16, 2.11.7 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-41666 has been found in github.com/argoproj/argo-cd/v2.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/argoproj/argo-cd/v2 to 2.9.21, 2.10.16, 2.11.7 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd/v2 CVE-2024-41666" on the vendor's site.
CVE-2024-41666 (github.com/argoproj/argo-cd/v2) — CWE-269
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.9.21, 2.10.16, 2.11.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in github.com/argoproj/argo-cd/v2.
Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd/v2.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.9.21, 2.10.16, 2.11.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/argoproj/argo-cd/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/argoproj/argo-cd/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/argoproj/argo-cd/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/argoproj/argo-cd/v2 to 2.9.21, 2.10.16, 2.11.7ステージング環境で 2.9.21, 2.10.16, 2.11.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- report drive.google.com
- web nvd.nist.gov
- web pkg.go.dev