dbcve.org
Argo CdApplication · Argoproj

CVE-2022-31105

CRITICAL · 9.6 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 2.2.11 / 2.3.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Argo CD has an improper certificate validation vulnerability in its OpenID Connect (OIDC) authentication. The bug allows Argo CD to trust malicious or untrustworthy OIDC providers due to insufficient/missing certificate validation when connecting to external identity providers.

MitigationUpgrade Argo CD to version 2.2.11, 2.3.6, or 2.4.5 or later. As a partial workaround, configure oidc.config.rootCA in the argocd-cm ConfigMap (note: this only validates certs during login flows, not token verification on API calls).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Argo CdApplication
Affected:>= 2.3.0, < 2.3.6>= 2.4.0, < 2.4.5
Argo CdApplication
Affected:>= 0.4.0, < 2.2.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Argo CD version
    Run 'argocd version' CLI or inspect the container image tag in the Argo CD deployment/statefulset
    Affected if Version is 2.3.0 to 2.3.5, 2.4.0 to 2.4.4, or 0.4.0 to 2.2.10 (Linuxfoundation variant)
  2. Identify if OIDC authentication is configured
    Inspect the argocd-cm ConfigMap in the Argo CD namespace and look for the oidc.config section
    Affected if OIDC provider is configured (url, issuer fields present) and the rootCA field is absent from oidc.config
  3. Check for explicit certificate validation
    Review the argocd-cm ConfigMap for the oidc.config.rootCA field and verify it contains a valid certificate
    Affected if The rootCA field is missing, empty, or does not contain a valid CA certificate

You are affected if an external OIDC provider is configured without explicit rootCA and your Argo CD version falls within the vulnerable ranges (2.3.0-2.3.5, 2.4.0-2.4.4, or 0.4.0-2.2.10 for Linuxfoundation).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.11 / 2.3.6 / 2.4.5 or later
Fixed in 2.2.112.3.62.4.5
Interim mitigation

Upgrade Argo CD to version 2.2.11, 2.3.6, or 2.4.5 or later. As a partial workaround, configure oidc.config.rootCA in the argocd-cm ConfigMap (note: this only validates certs during login flows, not token verification on API calls).

Recommended fix High confidence

2.4.5 (for 2.4.x) | 2.3.6 (for 2.3.x) | 2.2.11 (for 2.2.x and earlier)

  1. 1. Identify your current Argo CD version using: kubectl get deployment argocd-server -n argocd -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. 2. Determine which release branch you're on (2.2.x, 2.3.x, or 2.4.x) to select the appropriate upgrade path
  3. 3. Back up your Argo CD configuration: kubectl get configmap argocd-cm -n argocd -o yaml > argocd-cm-backup.yaml
  4. 4. For Argo CD 2.4.x: Upgrade to version 2.4.5 or later
  5. 5. For Argo CD 2.3.x: Upgrade to version 2.3.6 or later
  6. 6. For Argo CD 0.4.0 - 2.2.x: Upgrade to version 2.2.11
  7. 7. If using an external OIDC provider and immediate upgrade is not possible, apply partial mitigation by adding the `oidc.config.rootCA` field to the argocd-cm ConfigMap with your OIDC provider's root CA certificate
  8. 8. After upgrade, verify Argo CD is functioning: kubectl get pods -n argocd

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Argo Cd Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31105 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data