Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
| No fix yet |
| github.com/argoproj/argo-cd/v2 Go |
|
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
| No fix yet |
| github.com/argoproj/argo-cd/v2 Go |
|
|
Argo CD is a declarative continuous deployment framework for Kubernetes. In Argo CD versions prior to 2.3 (starting at least in v0.1.0, but likely in any version using Helm before 2.3), using a specifically-crafted Helm file could reference external Helm charts handled by the same repo-server to leak values, or files from the referenced Helm Chart. This was possible because Helm paths were predictable. The vulnerability worked by adding a Helm chart that referenced Helm resources from predictable paths. Because the paths of Helm charts were predictable and available on an instance of repo-server, it was possible to reference and then render the values and resources from other existing Helm charts regardless of permissions. While generally, secrets are not stored in these files, it was nevertheless possible to reference any values from these charts. This issue was fixed in Argo CD 2.3 and subsequent versions by randomizing Helm paths. User's still using Argo CD 2.3 or below are advised to update to a supported version. If this is not possible, disabling Helm chart rendering, or using an additional repo-server for each Helm chart would prevent possible exploitation.
From the CVE record · GitHub_M
In Argo CD before 2.3, predictable Helm paths let a specially crafted chart reference and render values or files from other charts handled by the same repo-server, regardless of permissions. Exploitation requires adding that crafted Helm chart; the input does not specify an authentication requirement or user interaction.
Teams running Argo CD before 2.3, including users of github.com/argoproj/argo-cd/v2 before 2.3.0 or the github.com/argoproj/argo-cd package, should check their deployments.