github.com/argoproj/argo-cd/v2
Affected
- introduced
2.2.0, fixed2.6.15(semver)
Fixed versions
2.6.15
Fix
- Fixed version
2.6.15go get github.com/argoproj/argo-cd/[email protected]
Advisory
Also known as: BIT-argo-cd-2023-40029, CVE-2023-40029, GO-2023-2049
Argo CD cluster secret might leak in cluster details page
Impact
Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored inkubectl.kubernetes.io/last-applied-configuration annotation.
https://github.com/argoproj/argo-cd/pull/7139 introduced the ability to manage cluster labels and annotations. Since clusters are stored as secrets it also exposes the kubectl.kubernetes.io/last-applied-configuration annotation which includes full secret body. In order to view the cluster annotations via the Argo CD API, the user must have clusters, get RBAC access.
Note: In many cases, cluster secrets do not contain any actually-secret information. But sometimes, as in bearer-token auth, the contents might be very sensitive.
Patches
The bug has been patched in the following versions:
Workarounds
Update/Deploy cluster secret with server-side-apply flag which does not use or rely on kubectl.kubernetes.io/last-applied-configuration annotation. Note: annotation for existing secrets will require manual removal.
For more information
Critical Basis: The source's own band: CRITICAL
2.2.0, fixed 2.6.15 (semver)2.6.15
2.6.15go get github.com/argoproj/argo-cd/[email protected]2.7.0, fixed 2.7.14 (semver)2.7.14
2.7.14go get github.com/argoproj/argo-cd/[email protected]2.8.0, fixed 2.8.3 (semver)2.8.3
2.8.3go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0