CVE-2024-31989 Affecting argo-cd-fips-2.10 package, versions <2.10.10-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (16th 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-6968886
  • published22 May 2024
  • disclosed21 May 2024

Introduced: 21 May 2024

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

How to fix?

Upgrade Chainguard argo-cd-fips-2.10 to version 2.10.10-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. It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS cluster, it requires manual enablement through configuration to enforce network policies. This raises concerns that many clients might unknowingly have open access to their Redis servers. This vulnerability could lead to Privilege Escalation to the level of cluster controller, or to information leakage, affecting anyone who does not have strict access controls on their Redis instance. This issue has been patched in version(s) 2.8.19, 2.9.15 and 2.10.10.