Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd Go |
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd Go |
all versions| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 0.7.0 and prior to versions 2.1.15m 2.2.9, and 2.3.4 is vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive 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 directory-type Application may commit a symlink which points to an out-of-bounds 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 JSON-formatted secrets which have been mounted as files on the repo-server. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. Users of versions 2.3.0 or above who do not have any Jsonnet/directory-type Applications may disable the Jsonnet/directory config management tool as a workaround.
From the CVE record · GitHub_M
Argo CD's repo-server follows symlinks committed to repositories used by directory-type Applications. A malicious user with repository write access can use this to leak sensitive files from the repo-server; no further user interaction is described.
Check Argo CD installations using github.com/argoproj/argo-cd/v2 before 2.1.15, from 2.2.0 to before 2.2.9, or from 2.3.0 to before 2.3.4, as well as users of the github.com/argoproj/argo-cd package, for which no fix is listed.