Skip to content
Fencer Vulns
high 8.3

CVE-2022-31105 json

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

published 2022-07-12 4 y ago modified 2026-06-17 4 mo ago also GHSA-7943-82jg-wmw5 , GO-2022-0518 , EUVD-2022-6279

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

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.

Patch / fix

  • go github.com/argoproj/argo-cd 2.2.11, 2.3.6, 2.4.5
  • go github.com/argoproj/argo-cd/v2 2.2.11, 2.3.6, 2.4.5
  • argoproj argo_cd 2.3.6, 2.4.5
  • linuxfoundation argo-cd 2.2.11

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-31105 updated cvss 8.3

argo-cd: certificate verification is skipped for connections to OIDC providers

  • Red Hat OpenShift GitOps openshift-gitops-1/argocd-rhel8, openshift-gitops-1/gitops-rhel8, openshift-gitops-1/applicationset-rhel8, openshift-gitops-1/gitops-rhel8-operator
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P
GitHub 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd
>=0.4.0, <2.2.11
>=2.3.0, <2.3.6
>=2.4.0, <2.4.5
>=0.4.0
2.2.11
2.3.6
2.4.5
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

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-599 Missing Validation of OpenSSL Certificate

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.