{"id":"CVE-2024-29893","aliases":["GHSA-jhwx-mhww-rgc3","BIT-argo-cd-2024-29893","GO-2024-2667"],"title":"ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability","summary":"ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","vendor":"argoproj","product":"github.com/argoproj/argo-cd/v2","ecosystem":"go","affected":["github.com/argoproj/argo-cd/v2 >= 2.4.0, < 2.8.14","github.com/argoproj/argo-cd/v2 >= 2.9.0, < 2.9.10","github.com/argoproj/argo-cd/v2 >= 2.10.0, < 2.10.5"],"patched":["github.com/argoproj/argo-cd/v2 2.8.14","github.com/argoproj/argo-cd/v2 2.9.10","github.com/argoproj/argo-cd/v2 2.10.5"],"published":"2024-03-29","updated":"2026-08-07","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-jhwx-mhww-rgc3","references":[{"url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29893"},{"url":"https://github.com/argoproj/argo-cd/commit/14f681e3ee7c38731943b98f92277e88a3db109d"},{"url":"https://github.com/argoproj/argo-cd/commit/36b8a12a38f8d92d55bffc81deed44389bf6eb59"},{"url":"https://github.com/argoproj/argo-cd/commit/3e5a878f6e30d935fa149723ea2a2e93748fcddd"},{"url":"https://github.com/argoproj/argo-cd"}],"tags":["osv","go"],"epss":0.00972,"epssPercentile":0.59937,"ingestedAt":"2026-08-07T19:14:17.315Z","slug":"CVE-2024-29893","body":"## Overview\n\n### Impact\nAll 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.\nThe 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.\n\n### Patches\nA patch for this vulnerability has been released in the following Argo CD versions:\n\nv2.10.5\nv2.9.10\nv2.8.14\n\n### For more information\nIf you have any questions or comments about this advisory:\n\nOpen an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\nJoin us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd\n\n\n### Credits\nThis vulnerability was found & reported by Jakub Ciolek\n\nThe Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue\n\n## Affected packages\n\n- `github.com/argoproj/argo-cd/v2 >= 2.4.0, < 2.8.14`\n- `github.com/argoproj/argo-cd/v2 >= 2.9.0, < 2.9.10`\n- `github.com/argoproj/argo-cd/v2 >= 2.10.0, < 2.10.5`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/argoproj/argo-cd/v2 2.8.14`\n- `github.com/argoproj/argo-cd/v2 2.9.10`\n- `github.com/argoproj/argo-cd/v2 2.10.5`","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0.2,"exploitation":0,"ransomware":0},"changes":[]}