CVE-2024-41666 Affecting argo-cd-2.9 package, versions <2.9.21-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.07% (35th 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-ARGOCD29-7647429
  • published8 Aug 2024
  • disclosed24 Jul 2024

Introduced: 24 Jul 2024

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

How to fix?

Upgrade Chainguard argo-cd-2.9 to version 2.9.21-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-cd-2.9 package and not the argo-cd-2.9 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. Argo CD has a Web-based terminal that allows users to get a shell inside a running pod, just as they would with kubectl exec. Starting in version 2.6.0, when the administrator enables this function and grants permission to the user p, role:myrole, exec, create, */*, allow, even if the user revokes this permission, the user can still perform operations in the container, as long as the user keeps the terminal view open for a long time. Although the token expiration and revocation of the user are fixed, however, the fix does not address the situation of revocation of only user p, role:myrole, exec, create, */*, allow permissions, which may still lead to the leakage of sensitive information. A patch for this vulnerability has been released in Argo CD versions 2.11.7, 2.10.16, and 2.9.21.

CVSS Scores

version 3.1