Cross-Site Scripting (XSS) in github.com/argoproj/argo-cd/v2 (CVE-2021-23347)
Summary
Cross-site scripting in github.com/argoproj/argo-cd/v2 (CVE-2021-23347). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.6 or later.
Original description
The description as published by the source.
The package github.com/argoproj/argo-cd/cmd before 1.7.13, from 1.8.0 and before 1.8.6 are vulnerable to Cross-site Scripting (XSS) the SSO provider connected to Argo CD would have to send back a malicious error message containing JavaScript to the user.
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-2021-23347 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 1.8.6 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd/v2 CVE-2021-23347" on the vendor's site.
CVE-2021-23347 (github.com/argoproj/argo-cd/v2) — CWE-79
Attack vector: remote (network-reachable)
Patched: 1.8.6 — 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.
Cross-site scripting (XSS) (CWE-79) 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 1.8.6.
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 1.8.6ステージング環境で 1.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory snyk.io
- patch github.com
- web github.com