# CVE-2022-24731: Path traversal allows leaking out-of-bound files from Argo CD repo-server > A malicious user with application update access can leak sensitive files from the Argo CD repo-server via path traversal in Helm charts. - **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Mar 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-h6h5-6fmq-rh28, GO-2022-0358 ## What is CVE-2022-24731? CVE-2022-24731 is a medium-severity path traversal vulnerability in Argoproj Argo Cd, published on 23 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 1.5.0 but before versions 2.1.11, 2.2.6, and 2.3.0 is vulnerable to a path traversal vulnerability, allowing a malicious user with read/write access to leak sensitive files from Argo CD's repo-server. A malicious Argo CD user who has been granted `create` or `update` access to Applications can leak the contents of any text file on the repo-server. By crafting a malicious Helm chart and using it in an Application, the attacker can retrieve the sensitive file's contents either as part of the generated manifests or in an error message. The attacker would have to know or guess the location of the target file. Sensitive files which could be leaked include files from another Application's source repositories or any secrets which have been mounted as files on the repo-server. This vulnerability is patched in Argo CD versions 2.1.11, 2.2.6, and 2.3.0. The problem can be mitigated by avoiding storing secrets in git, avoiding mounting secrets as files on the repo-server, avoiding decrypting secrets into files on the repo-server, and carefully limiting who can `create` or `update` Applications. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-284 (Improper Access Control), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2022-24731? 8 open source packages ship an affected version, including github.com/argoproj/argo-cd and github.com/argoproj/argo-cd/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd` | Go | From 1.5.0 | None | | `github.com/argoproj/argo-cd` | Go | From 1.5.0 | 2.1.11 | | `github.com/argoproj/argo-cd` | Go | From 1.5.0 | 2.1.11 | | `github.com/argoproj/argo-cd` | Go | From 2.2.0 | 2.2.6 | | `github.com/argoproj/argo-cd` | Go | From 2.2.0 | 2.2.6 | | `github.com/argoproj/argo-cd` | Go | From 2.3.0-rc1 | 2.3.0 | | `github.com/argoproj/argo-cd` | Go | From 2.3.0-rc1 | 2.3.0 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.1.11, 2.2.6, 2.3.0 | Products: Argoproj Argo Cd. ## How do I fix CVE-2022-24731? Upgrade github.com/argoproj/argo-cd to a fixed version for your release line: 2.1.11, 2.2.6 or 2.3.0. ## Is CVE-2022-24731 being exploited? There is no known exploitation of CVE-2022-24731 in the wild and no public exploit code. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24731 and fix it if it is affected. What it is: CVE-2022-24731 is a medium-severity path traversal vulnerability in Argoproj Argo Cd, published on 23 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-24731 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd (Go): affected from 1.5.0; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.5.0; fixed in 2.1.11 - github.com/argoproj/argo-cd (Go): affected from 1.5.0; fixed in 2.1.11 - github.com/argoproj/argo-cd (Go): affected from 2.2.0; fixed in 2.2.6 - github.com/argoproj/argo-cd (Go): affected from 2.2.0; fixed in 2.2.6 - github.com/argoproj/argo-cd (Go): affected from 2.3.0-rc1; fixed in 2.3.0 - github.com/argoproj/argo-cd (Go): affected from 2.3.0-rc1; fixed in 2.3.0 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.11, 2.2.6, 2.3.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-24731/ (Markdown: https://insights.sbomify.com/CVE-2022-24731/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24731 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24731 - OSV: https://osv.dev/vulnerability/CVE-2022-24731 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24731/ Summaries are generated and may contain mistakes; the official description above is the record.