CVE-2022-24905

Patched versions

A patch for this vulnerability has been released in the following Argo CD versions:

• v2.3.4
• v2.2.9
• v2.1.15

Workarounds

No workaround available.

Mitigations

It is advised to update to an Argo CD version containing a fix for this issue (see Patched versions above).

Credits

This vulnerability was discovered by Naufal Septiadi ([email protected]) and reported to us in a responsible way.

For more information

• Open an issue in the Argo CD issue tracker or discussions
• Join us on Slack in channel #argo-cd

A vulnerability was found in Argo CD that allows an attacker to spoof error messages on the login screen when 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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-24905 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.4, 2.2.9, 2.1.15); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-24905? CVE-2022-24905 is a medium-severity improper input validation vulnerability in github.com/argoproj/argo-cd/v2 (go), affecting versions >= 2.3.0, < 2.3.4. It is fixed in 2.3.4, 2.2.9, 2.1.15. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-24905? CVE-2022-24905 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-24905?
   • github.com/argoproj/argo-cd/v2 (go) (versions >= 2.3.0, < 2.3.4)
   • github.com/argoproj/argo-cd (go) (versions <= 1.8.7)
4. Is there a fix for CVE-2022-24905? Yes. CVE-2022-24905 is fixed in 2.3.4, 2.2.9, 2.1.15. Upgrade to this version or later.
5. Is CVE-2022-24905 exploitable, and should I be worried? Whether CVE-2022-24905 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-24905 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-24905?
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.3.4 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.2.9 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.1.15 or later
   • Upgrade github.com/argoproj/argo-cd to 2.1.15 or later