CVE-2023-40029

Argo CD cluster secret might leak in cluster details page

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

• Open an issue in the Argo CD issue tracker or discussions
• Join us on Slack in channel #argo-cd

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.

CVE-2023-40029 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.15, 2.7.14, 2.8.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The bug has been patched in the following versions:

• 2.8.3
• 2.7.14
• 2.6.15

1. What is CVE-2023-40029? CVE-2023-40029 is a critical-severity security vulnerability in github.com/argoproj/argo-cd/v2 (go), affecting versions >= 2.2.0, < 2.6.15. It is fixed in 2.6.15, 2.7.14, 2.8.3.
2. How severe is CVE-2023-40029? CVE-2023-40029 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/argoproj/argo-cd/v2 are affected by CVE-2023-40029? github.com/argoproj/argo-cd/v2 (go) versions >= 2.2.0, < 2.6.15 is affected.
4. Is there a fix for CVE-2023-40029? Yes. CVE-2023-40029 is fixed in 2.6.15, 2.7.14, 2.8.3. Upgrade to this version or later.
5. Is CVE-2023-40029 exploitable, and should I be worried? Whether CVE-2023-40029 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-40029 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-40029?
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.6.15 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.7.14 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.8.3 or later

Other vulnerabilities in github.com/argoproj/argo-cd/v2