CVE-2022-31105: Argo CD's certificate verification is skipped for connections to OIDC providers
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 Software
Event History
Frequently Asked Questions
What is CVE-2022-31105?
CVE-2022-31105 is a vulnerability in Argo CD, a declarative GitOps continuous delivery tool for Kubernetes, that could allow Argo CD to trust a malicious or untrustworthy OpenID Connect (OIDC) server.
What is the severity of CVE-2022-31105?
The severity of CVE-2022-31105 is critical with a CVSS score of 9.6.
Which versions of Argo CD are affected by CVE-2022-31105?
Argo CD versions 0.4.0 to 2.2.11, 2.3.0 to 2.3.6, and 2.4.0 to 2.4.5 are affected by CVE-2022-31105.
How can I fix CVE-2022-31105?
To fix CVE-2022-31105, update your Argo CD installation to version 2.2.11, 2.3.6, or 2.4.5.
Where can I find more information about CVE-2022-31105?
You can find more information about CVE-2022-31105 in the Argo CD releases page and the Argo CD security advisories page on GitHub.