# CVE-2024-37152: Unauthenticated Access to sensitive settings in Argo CD > Attackers can access sensitive Argo CD settings without authentication via the API, exposing configuration details. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jun 2024 - **Updated:** 2 Aug 2024 - **Also known as:** BIT-argo-cd-2024-37152, GHSA-87p9-x75h-p4j2, GO-2024-2902 ## What is CVE-2024-37152? CVE-2024-37152 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The vulnerability allows unauthorized access to the sensitive settings exposed by /api/v1/settings endpoint without authentication. All sensitive settings are hidden except passwordPattern. This vulnerability is fixed in 2.11.3, 2.10.12, and 2.9.17. Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2024-37152? 9 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2/server, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.10.0 | 2.10.12 | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.10.0 | 2.10.12 | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.11.0 | 2.11.3 | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.11.0 | 2.11.3 | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.9.3 | 2.9.17 | | `github.com/argoproj/argo-cd/v2/server` | Go | From 2.9.3 | 2.9.17 | | `argo-cd` | Bitnami | From 2.9.3 | 2.11.3 | | `github.com/argoproj/argo-cd` | Go | All versions | None | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.3 | 2.9.17, 2.10.12, 2.11.3 | Products: Argoproj Argo Cd. ## How do I fix CVE-2024-37152? Upgrade github.com/argoproj/argo-cd/v2/server to a fixed version for your release line: 2.10.12, 2.11.3 or 2.9.17. ## Is CVE-2024-37152 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37152 exists. Public exploit code: - Argo CD Unauthenticated Access to sensitive setting (nuclei): http/cves/2024/CVE-2024-37152.yaml ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-37152 and fix it if it is affected. What it is: CVE-2024-37152 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37152 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.10.0; fixed in 2.10.12 - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.10.0; fixed in 2.10.12 - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.11.0; fixed in 2.11.3 - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.11.0; fixed in 2.11.3 - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.9.3; fixed in 2.9.17 - github.com/argoproj/argo-cd/v2/server (Go): affected from 2.9.3; fixed in 2.9.17 - argo-cd (Bitnami): affected from 2.9.3; fixed in 2.11.3 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.3; fixed in 2.9.17, 2.10.12, 2.11.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-37152/ (Markdown: https://insights.sbomify.com/CVE-2024-37152/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37152 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37152 - OSV: https://osv.dev/vulnerability/CVE-2024-37152 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-37152/ Summaries are generated and may contain mistakes; the official description above is the record.