Argo CD does not scrub secret values from patch errors
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 |
≤ 1.8.7all versions| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A vulnerability was discovered in Argo CD that exposed secret values in error messages and the diff view when an invalid Kubernetes Secret resource was synced from a repository. The vulnerability assumes the user has write access to the repository and can exploit it, either intentionally or unintentionally, by committing an invalid Secret to repository and triggering a Sync. Once exploited, any user with read access to Argo CD can view the exposed secret data. The vulnerability is fixed in v2.13.4, v2.12.10, and v2.11.13.
From the CVE record · GitHub_M
Argo CD can expose secret values in error messages and the diff view when an invalid Kubernetes Secret is synced from a repository. A user with repository write access can commit an invalid Secret and trigger a Sync; afterward, any user with Argo CD read access can view the exposed data.
Check Argo CD installations using github.com/argoproj/argo-cd/v2 before 2.11.13, from 2.12.0 to before 2.12.10, or from 2.13.0 to before 2.13.4, as well as installations using github.com/argoproj/argo-cd, for which no fixed version is listed.