# CVE-2023-40029: Cluster secret might leak in cluster details page in Argo CD > Attackers with cluster read access can view sensitive cluster secret data exposed via Kubernetes annotations in Argo CD. - **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Sep 2023 - **Updated:** 26 Sep 2024 - **Also known as:** BIT-argo-cd-2023-40029, GHSA-fwr2-64vr-xv9m, GO-2023-2049 ## What is CVE-2023-40029? CVE-2023-40029 is a critical vulnerability in Argoproj Argo Cd, published on 7 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-40029? 9 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.2.0 | 2.6.15, 2.7.14, 2.8.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.2.0 | 2.6.15 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.2.0 | 2.6.15 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.3 | | `argo-cd` | Bitnami | From 2.2.0 | 2.6.15, 2.7.14, 2.8.3 | | `github.com/argoproj/argo-cd` | Go | All versions | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2023-40029? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.6.15, 2.7.14 or 2.8.3. ## Is CVE-2023-40029 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40029 exists. Public exploit code: - CVE-2023-40029 git (github_poc): https://github.com/guobei233/CVE-2023-40029 ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) - [CVE-2026-42880](https://insights.sbomify.com/CVE-2026-42880/): ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-40029 and fix it if it is affected. What it is: CVE-2023-40029 is a critical vulnerability in Argoproj Argo Cd, published on 7 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40029 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.6.15, 2.7.14, 2.8.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.6.15 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.6.15 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.3 - argo-cd (Bitnami): affected from 2.2.0; fixed in 2.6.15, 2.7.14, 2.8.3 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-40029/ (Markdown: https://insights.sbomify.com/CVE-2023-40029/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40029 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40029 - OSV: https://osv.dev/vulnerability/CVE-2023-40029 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-40029/ Summaries are generated and may contain mistakes; the official description above is the record.