Skip to content
Fencer Vulns
medium 4.3

CVE-2024-36106 json

Argo CD allows authenticated users to enumerate clusters by name

published 2024-06-06 2 y ago modified 2026-09-10 1 mo ago also BIT-argo-cd-2024-36106 , EUVD-2024-1898 , GHSA-3cqf-953p-h5cp , GO-2024-2898

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

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It’s possible for authenticated users to enumerate clusters by name by inspecting error messages. It’s also possible to enumerate the names of projects with project-scoped clusters if you know the names of the clusters. This vulnerability is fixed in 2.11.3, 2.10.12, and 2.9.17.

Patch / fix

  • go github.com/argoproj/argo-cd 2.9.17, 2.10.12, 2.11.3
  • bitnami argo-cd 2.11.3
  • go github.com/argoproj/argo-cd/v2 2.9.17, 2.10.12, 2.11.3
  • argoproj argo_cd 2.10.12, 2.11.3
  • linuxfoundation argo-cd 2.10.12, 2.11.3
  • linuxfoundation argo_continuous_delivery 2.10.12, 2.11.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-2024-36106 updated cvss 4.3

argo-cd: Error messages contain sensitive information

  • Red Hat OpenShift GitOps openshift-gitops-1/argocd-rhel8, openshift-gitops-1/argocd-rhel9, openshift-gitops-1/gitops-rhel8, openshift-gitops-1/gitops-rhel8-operator, openshift-gitops-1/gitops-operator-bundle
    affected: no fix planned “Will not fix”
  • Red Hat Openshift Data Foundation 4 odf4/odr-rhel8-operator
    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
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd
>=0.11.0, <2.9.17
>=2.10.0, <2.10.12
>=2.11.0, <2.11.3
>=0.11.0
2.9.17
2.10.12
2.11.3
bitnami argo-cd
>=2.10.0, <2.11.3
2.11.3
go github.com/argoproj/argo-cd/v2
<2.9.17
>=2.10.0, <2.10.12
>=2.11.0, <2.11.3
2.9.17
2.10.12
2.11.3

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.