Skip to content
Threat Brief

← All advisories

CVE-2022-24905

Medium 4.3No known exploitationFix available

Argo CD login screen allows message spoofing if SSO is enabled

Vendor advisory: GHSA-xmg8-99r8-jc2j

Record last updated

CVSS score

4.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

1.3%

Higher than 71% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A vulnerability was found in Argo CD prior to versions 2.3.4, 2.2.9, and 2.1.15 that allows an attacker to spoof error messages on the login screen when single sign on (SSO) is enabled. In order to exploit this vulnerability, an attacker would have to trick the victim to visit a specially crafted URL which contains the message to be displayed. As far as the research of the Argo CD team concluded, it is not possible to specify any active content (e.g. Javascript) or other HTML fragments (e.g. clickable links) in the spoofed message. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. There are currently no known workarounds.

Weakness: CWE-20

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
argoprojargo-cd< 2.1.15Not documentedCVE Program
argoprojargo-cd>= 2.2.0, < 2.2.9Not documentedCVE Program
argoprojargo-cd>= 2.3.0, < 2.3.4Not documentedCVE Program
gogithub.com/argoproj/argo-cdall versions up to and including 1.8.72.1.15GitHub Advisory Database
gogithub.com/argoproj/argo-cd/v2from 2.0.0 before 2.1.152.1.15GitHub Advisory Database
gogithub.com/argoproj/argo-cd/v2from 2.2.0 before 2.2.92.2.9GitHub Advisory Database
gogithub.com/argoproj/argo-cd/v2from 2.3.0 before 2.3.42.3.4GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references