CVE-2021-23347: GO-2022-0869 - Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd

CVE-2021-23347 · Severity: low · CVSS 3.1 · Published 2024-08-21

Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd

Technologies: github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2021-23347 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-23347 being exploited in the wild.
How severe is CVE-2021-23347?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/argoproj/argo-cd (Go) SEMVER:introduced=0,fixed=1.7.13,introduced=1.8.0,fixed=1.8.6; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=1.7.13.
Is there a fix for CVE-2021-23347?
Yes. github.com/argoproj/argo-cd (Go): upgrade to 1.8.6 or later; github.com/argoproj/argo-cd/v2 (Go): upgrade to 1.7.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-23347?
Check whether you run github.com/argoproj/argo-cd (Go) or github.com/argoproj/argo-cd/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/argoproj/argo-cd (Go): upgrade to 1.8.6 or later
    go get github.com/argoproj/argo-cd@v1.8.6
  • github.com/argoproj/argo-cd/v2 (Go): upgrade to 1.7.13 or later
    go get github.com/argoproj/argo-cd/v2@v1.7.13

Affected products

  • github.com/argoproj/argo-cd (Go) SEMVER:introduced=0,fixed=1.7.13,introduced=1.8.0,fixed=1.8.6
  • github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=1.7.13

Identifiers

  • CVE-2021-23347
  • GHSA-qq5v-f4c3-395c
  • GO-2022-0869

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.