CVE-2023-50726 Affecting argo-cd-fips-2.10 package, versions <2.10.3-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-6514693
  • published30 Mar 2024
  • disclosed13 Mar 2024

Introduced: 13 Mar 2024

CVE-2023-50726  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-cd-fips-2.10 to version 2.10.3-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. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have create privileges but not override privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing applications, create RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version.