Uncontrolled Resource Consumption vulnerability in ArgoCD's repo server
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.8.14, 2.9.10, 2.10.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- 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/v2Go
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/v2Go
From 2.4.0 · fixed in 2.8.14
- github.com/argoproj/argo-cd/v2Go
From 2.9.0 · fixed in 2.9.10
- github.com/argoproj/argo-cd/v2Go
From 2.10.0 · fixed in 2.10.5