Authorization Flaw in github.com/argoproj/argo-cd (CVE-2024-31990)
Summary
Vulnerability in github.com/argoproj/argo-cd (CVE-2024-31990). Risk of unauthorized operations or information disclosure. Exploitable via demo. Mitigation: upgrade to 2.10.7 or later.
Original description
The description as published by the source.
Impact
I can convince the UI to let me do things with an invalid Application.
- Admin gives me
p, michael, applications, *, demo/*, allow, wheredemocan just deploy to thedemonamespace - Admin gives me AppProject
devwhich reconciles from nsdev-apps - Admin gives me
p, michael, applications, sync, dev/*, allow, i.e. no updating via the UI allowed, gitops-only - I create an Application called
pwnindev-appswith project dev and sync the app with sources from git - I change the Application’s project to demo via kubectl or gitops (whichever mechanism my admins have given me, because it should be safe)
- I use the UI to edit the resource which should only be mutable via gitops
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
v2.10.7
v2.9.12
v2.8.16
For more information
If you have any questions or comments about this advisory:
Open an issue in the Argo CD issue tracker or discussions
Join us on Slack in channel #argo-cd
Credits
This vulnerability was found & reported by @crenshaw-dev (Michael Crenshaw)
The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue
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-31990 has been found in github.com/argoproj/argo-cd.
Attackers can target a specific entry point like demo 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.10.7 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd CVE-2024-31990" on the vendor's site.
CVE-2024-31990 (github.com/argoproj/argo-cd) — CWE-863
Attack vector: remote (network-reachable)
Attack surface: demo / dev / pwn
Patched: 2.10.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.
Incorrect authorization (CWE-863) exists in github.com/argoproj/argo-cd. Attackers reach the vulnerable code path via demo.
Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd. Attack surface: demo / dev / pwn.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.10.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' . 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.10.7ステージング環境で 2.10.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com