github.com/argoproj/argo-cd/v2
Affected
- introduced
2.4.0, fixed2.8.14(semver)
Fixed versions
2.8.14
Fix
- Fixed version
2.8.14go get github.com/argoproj/argo-cd/[email protected]
Advisory
Also known as: BIT-argo-cd-2024-29893, CVE-2024-29893, GO-2024-2667
ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability
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
Medium Basis: The source's own band: MODERATE
2.4.0, fixed 2.8.14 (semver)2.8.14
2.8.14go get github.com/argoproj/argo-cd/[email protected]2.9.0, fixed 2.9.10 (semver)2.9.10
2.9.10go get github.com/argoproj/argo-cd/[email protected]2.10.0, fixed 2.10.5 (semver)2.10.5
2.10.5go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0