First published: Mon Jun 27 2022(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linuxfoundation Argo-cd | >=1.3.0<2.1.6 | |
Linuxfoundation Argo-cd | =2.2.9 | |
Linuxfoundation Argo-cd | =2.3.4 | |
Linuxfoundation Argo-cd | =2.4.0 | |
Argoproj Argo Cd | >=1.3.0<2.1.6 | |
Argoproj Argo Cd | =2.2.9 | |
Argoproj Argo Cd | =2.3.4 | |
Argoproj Argo Cd | =2.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-31036 is a vulnerability in Argo CD that allows a malicious user with repository write access to leak sensitive YAML files.
Argo CD is a declarative GitOps continuous delivery tool for Kubernetes.
All versions of Argo CD starting from v1.3.0 up to v2.4.0 are affected by CVE-2022-31036.
CVE-2022-31036 has a severity score of 4.3, which is considered medium severity.
To fix CVE-2022-31036, you should update Argo CD to a version that includes the fix, such as v2.4.1 or later.