Argo CD's certificate verification is skipped for connections to OIDC providers

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 0.4.0 and prior to 2.2.11, 2.3.6, and 2.4.5 is vulnerable to an improper certificate validation bug which could cause Argo CD to trust a malicious (or otherwise untrustworthy) OpenID Connect (OIDC) provider. A patch for this vulnerability has been released in Argo CD versions 2.4.5, 2.3.6, and 2.2.11. There are no complete workarounds, but a partial workaround is available. Those who use an external OIDC provider (not the bundled Dex instance), can mitigate the issue by setting the `oidc.config.rootCA` field in the `argocd-cm` ConfigMap. This mitigation only forces certificate validation when the API server handles login flows. It does not force certificate verification when verifying tokens on API calls.

Timeline

1. Jul 12, 2022, 10:05 PM UTCCVE published
2. Apr 23, 2025, 3:51 PM UTCCISA SSVC assessment

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

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

Affected versions

• argoproj argo-cd

  From 0.4.0 · fixed in 2.2.11; From 2.3.0 · fixed in 2.3.6; From 2.4.0 · fixed in 2.4.5

• github.com/argoproj/argo-cdGo

  From 0.4.0

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

  fixed in 2.2.11; From 2.3.0 · fixed in 2.3.6; From 2.4.0 · fixed in 2.4.5

• github.com/argoproj/argo-cdGo

  From 0.4.0 · fixed in 2.2.11

• github.com/argoproj/argo-cdGo

  From 2.3.0 · fixed in 2.3.6

• github.com/argoproj/argo-cdGo

  From 2.4.0 · fixed in 2.4.5

References 3