Information Disclosure in github.com/argoproj/argo-cd/v2 (CVE-2022-24348)
Summary
Vulnerability in github.com/argoproj/argo-cd/v2 (CVE-2022-24348). Confidential information can be exposed externally. Mitigation: upgrade to 2.2.4 or later.
Original description
The description as published by the source.
Impact
All versions of Argo CD are vulnerable to a path traversal bug that allows to pass arbitrary values files to be consumed by Helm charts.
Additionally, it is possible to craft special Helm chart packages containing value files that are actually symbolic links, pointing to arbitrary files outside the repository's root directory.
If an attacker with permissions to create or update Applications knows or can guess the full path to a file containing valid YAML, they can create a malicious Helm chart to consume that YAML as values files, thereby gaining access to data they would otherwise have no access to.
The impact can especially become critical in environments that make use of encrypted value files (e.g. using plugins with git-crypt or SOPS) containing sensitive or confidential data, and decrypt these secrets to disk before rendering the Helm chart.
Also, because any error message from helm template is passed back to the user, and these error messages are quite verbose, enumeration of files on the repository server's file system is possible.
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
- v2.3.0
- v2.2.4
- v2.1.9
We urge users of Argo CD to update their installation to one of the fixed versions as listed above.
Workarounds
No workaround for this issue.
References
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-2022-24348 has been found in github.com/argoproj/argo-cd/v2.
Confidential information can be exposed externally.
What to do: upgrade github.com/argoproj/argo-cd/v2 to 2.2.4 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd/v2 CVE-2022-24348" on the vendor's site.
CVE-2022-24348 (github.com/argoproj/argo-cd/v2) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.2.4 — 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.
Information disclosure (CWE-200) exists in github.com/argoproj/argo-cd/v2.
Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd/v2.
Severity: ?. Confidential information can be exposed externally.
Update to 2.2.4.
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.2.4ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 apiiro.com
- web github.com
- web github.com