Homepage

CVE-2024-29893 Affecting argo-cd-fips-2.10 package, versions <2.10.5-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-ARGOCDFIPS210-6514692
  • published30 Mar 2024
  • disclosed29 Mar 2024
Report a new vulnerability Found a mistake?

Introduced: 29 Mar 2024

CVE-2024-29893  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-cd-fips-2.10 to version 2.10.5-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-cd-fips-2.10 package and not the argo-cd-fips-2.10 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.