# CVE-2024-29893: Uncontrolled Resource Consumption vulnerability in ArgoCD's repo server > Attackers can crash the ArgoCD repo server by pointing it to a malicious Helm registry that exhausts memory, requiring a patch to mitigate. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Mar 2024 - **Updated:** 2 Aug 2024 - **Also known as:** BIT-argo-cd-2024-29893, GHSA-jhwx-mhww-rgc3, GO-2024-2667 ## What is CVE-2024-29893? CVE-2024-29893 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 29 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of ArgoCD starting from v2.4 have a bug where the ArgoCD repo-server component is vulnerable to a Denial-of-Service attack vector. Specifically, it's possible to crash the repo server component through an out of memory error by pointing it to a malicious Helm registry. The loadRepoIndex() function in the ArgoCD's helm package, does not limit the size nor time while fetching the data. It fetches it and creates a byte slice from the retrieved data in one go. If the registry is implemented to push data continuously, the repo server will keep allocating memory until it runs out of it. A patch for this vulnerability has been released in v2.10.3, v2.9.8, and v2.8.12. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2024-29893? 8 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.5 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.5 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.8.14, 2.9.10, 2.10.5 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.8.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.4.0 | 2.8.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.10 | | `argo-cd` | Bitnami | From 2.4.0 | 2.10.5 | Products: Argoproj Argo Cd. ## How do I fix CVE-2024-29893? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.10.5, 2.8.14 or 2.9.10. ## Is CVE-2024-29893 being exploited? There is no known exploitation of CVE-2024-29893 in the wild and no public exploit code. ## 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-29893 and fix it if it is affected. What it is: CVE-2024-29893 is a medium-severity denial of service vulnerability in Argoproj Argo Cd, published on 29 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-29893 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.8.14, 2.9.10, 2.10.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.8.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.8.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.10 - argo-cd (Bitnami): affected from 2.4.0; fixed in 2.10.5 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-29893/ (Markdown: https://insights.sbomify.com/CVE-2024-29893/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29893 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29893 - OSV: https://osv.dev/vulnerability/CVE-2024-29893 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-29893/ Summaries are generated and may contain mistakes; the official description above is the record.