Argo CD vulnerable to Uncontrolled Memory Consumption
- 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.1.16, 2.2.10, 2.3.5, 2.4.1
- 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 continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file. The fix for this vulnerability is available in versions 2.3.5, 2.2.10, 2.1.16, and later. There are no known workarounds. Users are recommended to upgrade.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- argoproj argo-cd
From 0.7.0 · fixed in 2.1.16; From 2.0.0 · fixed in 2.2.10; From 2.3.0 · fixed in 2.3.5
- github.com/argoproj/argo-cdGo
From 0.7.0 · fixed in 2.1.16
- github.com/argoproj/argo-cd/v2Go
fixed in 2.1.16
- github.com/argoproj/argo-cd/v2Go
From 2.2.0 · fixed in 2.2.10
- github.com/argoproj/argo-cd/v2Go
From 2.3.0 · fixed in 2.3.5
- github.com/argoproj/argo-cd/v2Go
From 2.4.0 · fixed in 2.4.1
- github.com/argoproj/argo-cdGo
From 0.7.0
- github.com/argoproj/argo-cd/v2Go
fixed in 2.1.16; From 2.2.0 · fixed in 2.2.10; From 2.3.0 · fixed in 2.3.5; From 2.4.0 · fixed in 2.4.1