Skip to content
OpenAdvisories
High · 8.3 CVE-2022-31105 EUVD-2022-6279GHSA-7943-82jg-wmw5GO-2022-0518

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

Published Jul 12, 2022 · Updated Apr 23, 2025 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
argoproj argo-cd >= 0.4.0, < 2.2.11, >= 2.3.0, < 2.3.6, >= 2.4.0, < 2.4.5 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/argoproj/argo-cd >= 0.4.0, < 2.2.11 2.2.11 GHSA-7943-82jg-wmw5
Go github.com/argoproj/argo-cd >= 2.3.0, < 2.3.6 2.3.6 GHSA-7943-82jg-wmw5
Go github.com/argoproj/argo-cd >= 2.4.0, < 2.4.5 2.4.5 GHSA-7943-82jg-wmw5
Go github.com/argoproj/argo-cd >= 0.4.0 — GO-2022-0518
Go github.com/argoproj/argo-cd/v2 < 2.2.11 · >= 2.3.0, < 2.3.6 · >= 2.4.0, < 2.4.5 2.2.11, 2.3.6, 2.4.5 GO-2022-0518

References