Skip to content
Fencer Vulns
critical 9.9

CVE-2023-40029 json

Cluster secret might leak in cluster details page in Argo CD

published 2023-09-07 3 y ago modified 2026-06-17 4 mo ago also BIT-argo-cd-2023-40029 , EUVD-2023-2497 , GHSA-fwr2-64vr-xv9m , GO-2023-2049

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.6.15, 2.7.14, 2.8.3
  • bitnami argo-cd 2.6.15, 2.7.14, 2.8.3
  • argoproj argo_cd 2.6.15, 2.7.14, 2.8.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-40029 updated cvss 9.9

ArgoCD: secrets can be leak through kubectl.kubernetes.io/last-applied-configuration

  • Red Hat OpenShift GitOps 1.8 openshift-gitops-1/argocd-rhel8 v1.8.5-1
    fixed: vendor fix RHSA-2023:5030
  • Red Hat OpenShift GitOps 1.9 openshift-gitops-1/argocd-rhel8 v1.9.2-2
    fixed: vendor fix RHSA-2023:5029
  • Red Hat OpenShift GitOps 1.8 openshift-gitops-1/dex-rhel8 v1.8.5-1, openshift-gitops-1/gitops-rhel8 v1.8.5-1, openshift-gitops-1/kam-delivery-rhel8 v1.8.5-1, openshift-gitops-1/console-plugin-rhel8 v1.8.5-1, openshift-gitops-1/gitops-rhel8-operator v1.8.5-1, openshift-gitops-1/gitops-operator-bundle v1.8.5-1 Red Hat OpenShift GitOps 1.9 openshift-gitops-1/dex-rhel8 v1.9.2-2, openshift-gitops-1/gitops-rhel8 v1.9.2-2, openshift-gitops-1/must-gather-rhel8 v1.9.2-2, openshift-gitops-1/kam-delivery-rhel8 v1.9.2-2, openshift-gitops-1/argo-rollouts-rhel8 v1.9.2-2, openshift-gitops-1/console-plugin-rhel8 v1.9.2-2, +2 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-fwr2-64vr-xv9m referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OSV 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
>=2.2.0, <2.6.15
>=2.7.0, <2.7.14
>=2.8.0, <2.8.3
2.6.15
2.7.14
2.8.3
bitnami argo-cd
>=2.2.0, <2.6.15
>=2.7.0, <2.7.14
>=2.8.0, <2.8.3
2.6.15
2.7.14
2.8.3
go github.com/argoproj/argo-cd
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.