CVE-2022-24905: GO-2022-0454 - Login screen allows message spoofing if SSO is enabled in github.com/argoproj/argo-cd

Quick answers

Is CVE-2022-24905 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-24905 being exploited in the wild.

How severe is CVE-2022-24905?

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, SEMVER:introduced=0,fixed=2.1.15; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.1.15,introduced=2.2.0,fixed=2.2.9,introduced=2.3.0,fixed=2.3.4, SEMVER:introduced=2.3.0,fixed=2.3.4.

Is there a fix for CVE-2022-24905?

Yes. github.com/argoproj/argo-cd (Go): upgrade to 2.1.15 or later; github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.3.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-24905?

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 2.1.15 or later

  go get github.com/argoproj/argo-cd@v2.1.15

• github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.3.4 or later

  go get github.com/argoproj/argo-cd/v2@v2.3.4

Affected products

• github.com/argoproj/argo-cd (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.1.15
• github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.1.15,introduced=2.2.0,fixed=2.2.9,introduced=2.3.0,fixed=2.3.4, SEMVER:introduced=2.3.0,fixed=2.3.4

Identifiers

• CVE-2022-24905
• GHSA-xmg8-99r8-jc2j
• GO-2022-0454