Argo CD's certificate verification is skipped for connections to OIDC providers
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
|
|
| github.com/argoproj/argo-cd/v2 |
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
|
|
| github.com/argoproj/argo-cd/v2 |
|
|
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.
From the CVE record · GitHub_M
Argo CD improperly validates certificates for OpenID Connect (OIDC) providers. This can cause it to trust a malicious or otherwise untrustworthy provider; attacker access requirements and user interaction are not specified.
Teams running Argo CD or the Go packages github.com/argoproj/argo-cd and github.com/argoproj/argo-cd/v2 should check versions before 2.2.11, 2.3.0 through 2.3.5, and 2.4.0 through 2.4.4.