CVE-2024-29893: Uncontrolled Resource Consumption vulnerability in ArgoCD's repo server
Impact 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.
Patches A patch for this vulnerability has been released in the following Argo CD versions:
v2.10.5 v2.9.10 v2.8.14
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 Jakub Ciolek
The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue
Other sources
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.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-29893?
CVE-2024-29893 is classified as a Denial-of-Service vulnerability affecting the ArgoCD repo-server.
How do I fix CVE-2024-29893?
To address CVE-2024-29893, upgrade your ArgoCD deployment to versions 2.10.5, 2.9.10, or 2.8.14.
Which versions of ArgoCD are affected by CVE-2024-29893?
All versions of ArgoCD starting from v2.4 and below v2.10.5 are affected by CVE-2024-29893.
What components are impacted by CVE-2024-29893?
CVE-2024-29893 impacts the ArgoCD repo-server component.
Can I prevent CVE-2024-29893 without upgrading?
No, the only effective remedy for CVE-2024-29893 is to upgrade to a secure version of ArgoCD.