CVE-2022-24730

Workarounds

The only certain way to avoid the vulnerability is to upgrade.

To mitigate the problem, you can

• avoid storing secrets in git
• avoid mounting secrets as files on the repo-server
• avoid decrypting secrets into files on the repo-server
• carefully limit who has get access for repositories

References

• Security documentation for the repo-server component
• Argo CD RBAC configuration documentation

For more information

Open an issue in the Argo CD issue tracker or discussions
Join us on Slack in channel #argo-cd

All unpatched versions of Argo CD starting with v1.3.0 are vulnerable to a path traversal bug, compounded by an improper access control bug, allowing a malicious user with read-only repository access to leak sensitive files from Argo CD's repo-server.

A malicious Argo CD user who has been granted get access for a repository containing a Helm chart can craft an API request to the /api/v1/repositories/{repo_url}/appdetails endpoint to leak the contents of out-of-bounds files from the repo-server.

The malicious payload would reference an out-of-bounds file, and the contents of that file would be returned as part of the response. Contents from a non-YAML file may be returned as part of 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 other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any secrets which have been mounted as files on the repo-server.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-24730 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.11, 2.2.6, 2.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

A patch for this vulnerability has been released in the following Argo CD versions:

• v2.3.0
• v2.2.6
• v2.1.11

The patches do two things:

1. prevent path traversal
2. limit /api/v1/repositories/{repo_url}/appdetails access to users who either A) have been granted Application create privileges or B) have been granted Application get privileges and are requesting details for a repo_url that has already been used for the given Application

1. What is CVE-2022-24730? CVE-2022-24730 is a high-severity path traversal vulnerability in github.com/argoproj/argo-cd (go), affecting versions >= 1.3.0, < 2.1.11. It is fixed in 2.1.11, 2.2.6, 2.3.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-24730? CVE-2022-24730 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/argoproj/argo-cd are affected by CVE-2022-24730? github.com/argoproj/argo-cd (go) versions >= 1.3.0, < 2.1.11 is affected.
4. Is there a fix for CVE-2022-24730? Yes. CVE-2022-24730 is fixed in 2.1.11, 2.2.6, 2.3.0. Upgrade to this version or later.
5. Is CVE-2022-24730 exploitable, and should I be worried? Whether CVE-2022-24730 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-24730 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-24730?
   • Upgrade github.com/argoproj/argo-cd to 2.1.11 or later
   • Upgrade github.com/argoproj/argo-cd to 2.2.6 or later
   • Upgrade github.com/argoproj/argo-cd to 2.3.0 or later

Other vulnerabilities in github.com/argoproj/argo-cd