CVE-2022-31036 Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server
A malicious user with repository write access can use symlinks to leak sensitive YAML files from the Argo CD repo-server.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-31036?
CVE-2022-31036 is a medium-severity path traversal vulnerability in Argoproj Argo Cd, published on 27 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.
Which versions are affected by CVE-2022-31036?
12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16, 2.2.10, 2.3.5, 2.4.1 |
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16 |
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.2.0 | 2.2.10 |
github.com/argoproj/argo-cd/v2 Go | From 2.2.0 | 2.2.10 |
github.com/argoproj/argo-cd/v2 Go | From 2.3.0 | 2.3.5 |
6 more packages
github.com/argoproj/argo-cd/v2 Go | From 2.3.0 | 2.3.5 |
github.com/argoproj/argo-cd/v2 Go | From 2.4.0 | 2.4.1 |
github.com/argoproj/argo-cd/v2 Go | From 2.4.0 | 2.4.1 |
github.com/argoproj/argo-cd Go | From 1.3.0 | None |
github.com/argoproj/argo-cd Go | From 1.3.0 | 2.1.16 |
github.com/argoproj/argo-cd Go | From 1.3.0 | 2.1.16 |
Products include Argoproj Argo Cd.
How do I fix CVE-2022-31036?
Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.1.16, 2.2.10, 2.3.5 or 2.4.1.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2022-31036 being exploited?
There is no known exploitation of CVE-2022-31036 in the wild and no public exploit code.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
Sources
Also known as GHSA-q4w5-4gq2-98vm, GO-2022-0499.