Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v3 Go |
|
|
| github.com/argoproj/argo-cd Go |
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v3 Go |
|
|
| github.com/argoproj/argo-cd Go |
all versions| No fix yet |
| github.com/argoproj/argo-cd/v2 Go |
| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.
From the CVE record · GitHub_M
Argo CD ServerSideDiff does not fully sanitize predicted live Kubernetes Secret objects. When a Secret contains values in the kubectl.kubernetes.io/last-applied-configuration annotation, those values can appear in UI or CLI diffs. The input does not specify an authentication requirement or additional user interaction.
Teams running Argo CD with github.com/argoproj/argo-cd/v3 versions >=3.2.0 <3.2.12, >=3.3.0-rc1 <3.3.10, or >=3.4.0-rc1 <3.4.2 should check; the input also lists all versions of the unversioned and /v2 Go packages as affected, with no fix.