Privilege Escalation in github.com/argoproj/argo-cd (CVE-2023-50726)
Summary
Vulnerability in github.com/argoproj/argo-cd (CVE-2023-50726). Risk of unauthorized operations or information disclosure. Exploitable via create. Mitigation: upgrade to 2.8.12 or later.
Original description
The description as published by the source.
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have create privileges but not override privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing applications, create RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version.
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-2023-50726 has been found in github.com/argoproj/argo-cd.
Attackers can target a specific entry point like create over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/argoproj/argo-cd to 2.8.12 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd CVE-2023-50726" on the vendor's site.
CVE-2023-50726 (github.com/argoproj/argo-cd) — CWE-269
Attack vector: remote (network-reachable) / no user interaction
Attack surface: create / override
Patched: 2.8.12 — 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. Attackers reach the vulnerable code path via create.
Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd. Attack surface: create / override.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.8.12.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/argoproj/argo-cdを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/argoproj/argo-cd to 2.8.12ステージング環境で 2.8.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web argo-cd.readthedocs.io