Insecure entropy in argo-cd

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact potentially granting an attacker admin access to Argo CD. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. There are no known workarounds for this vulnerability.

Timeline

1. Jun 27, 2022, 7:00 PM UTCCVE published
2. Apr 23, 2025, 3:52 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Apr 23, 2025, 6:08 PM UTCRecord last updated

Affected versions

• argoproj argo-cd

  From 0.11.0 · fixed in 2.1.16; From 2.2.0 · fixed in 2.2.10; From 2.3.0 · fixed in 2.3.5; From 2.4.0 · fixed in 2.4.1

• github.com/argoproj/argo-cdGo

  From 0.11.0 · fixed in 2.1.16

• github.com/argoproj/argo-cd/v2Go

  fixed in 2.1.16

• github.com/argoproj/argo-cd/v2Go

  From 2.2.0 · fixed in 2.2.10

• github.com/argoproj/argo-cd/v2Go

  From 2.3.0 · fixed in 2.3.5

• github.com/argoproj/argo-cd/v2Go

  From 2.4.0 · fixed in 2.4.1

• github.com/argoproj/argo-cdGo

  From 0.11.0

• github.com/argoproj/argo-cd/v2Go

  fixed in 2.1.16; From 2.2.0 · fixed in 2.2.10; From 2.3.0 · fixed in 2.3.5; From 2.4.0 · fixed in 2.4.1

References 2