CVE-2024-36106Public exploitNetwork attack vector

Authenticated cluster enumeration via distinguishable API errors

Published Jun 6, 2024 · Updated Sep 3, 2024

Information disclosure in affected Argo CD releases allows remote authenticated users to enumerate cluster and project names through API errors. The cluster API retrieves a named cluster before authorization and returns detailed permission-denied text for existing clusters but a generic denial for nonexistent names, creating an error oracle that also reveals a project name for project-scoped clusters. Any authenticated account that can query the cluster endpoint can distinguish valid names, but the disclosed data is limited to cluster and associated project identifiers.

CVSS severity4.3
Medium
EPSS probability0.41%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in affected Argo CD releases allows remote authenticated users to enumerate cluster and project names through API errors. The cluster API retrieves a named cluster before authorization and returns detailed permission-denied text for existing clusters but a generic denial for nonexistent names, creating an error oracle that also reveals a project name for project-scoped clusters. Any authenticated account that can query the cluster endpoint can distinguish valid names, but the disclosed data is limited to cluster and associated project identifiers.

The record

CVE
CVE-2024-36106
Published
Jun 6, 2024
Updated
Sep 3, 2024
Vendor
Argo Project
Product
Argo CD
Classifications
CWE-209, T1580
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 6, 2024CVE publishedPublication date reported by the CVE source.
  2. Sep 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=> 0.11.0, < 2.9.17
  2. Affected versionversion=>= 2.10.0, < 2.10.12
  3. Affected versionversion=>= 2.11.0, < 2.11.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Argo Project · Argo CDversion=> 0.11.0, < 2.9.17; version=>= 2.10.0, < 2.10.12; version=>= 2.11.0, < 2.11.3

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-209Generation of Error Message Containing Sensitive Information
T1580Cloud Infrastructure Discovery

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo