dbcve.org
Argo CdApplication · Argoproj

CVE-2022-31102

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 2.3.6 / 2.4.5 or later.
See remediation →
68/100
Remediation priority · Elevated
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 2.3.0 and prior to 2.3.6 and 2.4.5 is vulnerable to a cross-site scripting (XSS) bug which could allow an attacker to inject arbitrary JavaScript in the `/auth/callback` page in a victim's browser. This vulnerability only affects Argo CD instances which have single sign on (SSO) enabled. The exploit also assumes the attacker has 1) access to the API server's encryption key, 2) a method to add a cookie to the victim's browser, and 3) the ability to convince the victim to visit a malicious `/auth/callback` link. The vulnerability is classified as low severity because access to the API server's encryption key already grants a high level of access. Exploiting the XSS would allow the attacker to impersonate the victim, but would not grant any privileges which the attacker could not otherwise gain using the encryption key. A patch for this vulnerability has been released in the following Argo CD versions 2.4.5 and 2.3.6. There is currently no known workaround.

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 versions 2.3.0 through 2.3.5 and 2.4.0 through 2.4.4 contain a stored XSS vulnerability in the /auth/callback page. Attackers with access to the API server's encryption key can inject malicious JavaScript into the SSO callback handler, allowing session hijacking by impersonating victims. Exploitation requires SSO to be enabled and chaining multiple conditions (encryption key access, cookie injection, victim interaction).

MitigationUpgrade Argo CD to version 2.3.6 or 2.4.5 or later to patch this vulnerability. There is no workaround; instances with SSO enabled are affected.

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

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
Low
Integrity
Low
Availability
None

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

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. Identify installed Argo CD version
    Run 'argocd version' or check the deployment manifests/image tags to determine the exact version running in the cluster
    Affected if Version is 2.3.0 through 2.3.5 or 2.4.0 through 2.4.4
  2. Verify if SSO is enabled
    Check the Argo CD configmap or CRD for OIDC or OAuth provider configuration under the 'url' and 'dex' sections in the argocd-cm or ArgoCD CR
    Affected if SSO/OIDC/OAuth is configured and active in the Argo CD instance
  3. Confirm access to API server encryption key
    Review RBAC policies and access controls around the Argo CD API server deployment and any secrets containing 'encryption' or 'secretKey' in their names
    Affected if The API server's encryption key is accessible to untrusted users or stored without adequate protection

The environment is affected if the installed Argo CD version falls within 2.3.0-2.3.5 or 2.4.0-2.4.4 AND SSO is enabled AND the encryption key has insufficient access controls.

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.3.6 / 2.4.5 or later
Fixed in 2.3.62.4.5
Interim mitigation

Upgrade Argo CD to version 2.3.6 or 2.4.5 or later to patch this vulnerability. There is no workaround; instances with SSO enabled are affected.

Recommended fix High confidence

Upgrade to Argo CD 2.3.6 (if on 2.3.x branch) or 2.4.5 (if on 2.4.x branch)

  1. 1. Identify the current Argo CD version by running: kubectl get deployment argocd-server -n argocd -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. 2. If version is >= 2.3.0 and < 2.3.6, upgrade to version 2.3.6
  3. 3. If version is >= 2.4.0 and < 2.4.5, upgrade to version 2.4.5
  4. 4. For Kubernetes deployments, update the Argo CD image: kubectl set image deployment/argocd-server argocd-server=argoproj/argocd:<new-version> -n argocd
  5. 5. Verify the upgrade was successful by checking the Argo CD version again and ensuring all pods are running

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

Fix this in Argo Cd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31102 — 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-31102 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