CVE-2022-31034

Workarounds

There are no workarounds. You must upgrade to a patched version to resolve the vulnerability.

References

These are the insufficiently-random parameters:

1. (since 0.11.0) The state parameter generated by the argocd login command for Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entropy required in the spec. This parameter is a "recommended" part of the Oauth2 flow and helps protect against cross-site request forgery attacks.
2. (since 1.7.2, when PKCE was added) The code_verifier parameter generated by the argocd login command for Oauth2+PKCE login used a non-cryptographically secure source of entropy. The attacks mitigated by PKCE are complex but have been observed in the wild.
3. (since 0.11.0) The state parameter generated by the Argo CD API server during a UI-initiated Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entropy required in the spec. This parameter is a "recommended" part of the Oauth2 flow and helps protect against cross-site request forgery attacks.
4. (since 0.11.0) The nonce parameter generated by the Argo CD API server during a UI-initiated Oauth2 implicit flow login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide sufficient entropy. This parameter is a required part of the OIDC implicit login flow and helps protect against replay attacks.

Credits

Originally discovered by @jgwest. @jannfis and @crenshaw-dev re-discovered the vulnerability when reviewing notes from ADA Logics' security audit of the Argo project sponsored by CNCF and facilitated by OSTIF. Thanks to Adam Korczynski and David Korczynski for their work on the audit.

For more information

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

All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. (The specific weak parameters are listed in the References section.)

The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact (potentially granting an attacker admin access to Argo CD). The CVSS for this Security Advisory assumes the worst-case scenario.

Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.

CVE-2022-31034 has a CVSS score of 8.3 (High). 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.1.16, 2.2.10, 2.3.5, 2.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

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

• v2.4.1
• v2.3.5
• v2.2.10
• v2.1.16

1. What is CVE-2022-31034? CVE-2022-31034 is a high-severity use of insufficiently random values vulnerability in github.com/argoproj/argo-cd (go), affecting versions >= 0.11.0, <= 1.8.7. It is fixed in 2.1.16, 2.2.10, 2.3.5, 2.4.1. Security-sensitive operations rely on values that are predictable or insufficiently random.
2. How severe is CVE-2022-31034? CVE-2022-31034 has a CVSS score of 8.3 (High). 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-31034?
   • github.com/argoproj/argo-cd (go) (versions >= 0.11.0, <= 1.8.7)
   • github.com/argoproj/argo-cd/v2 (go) (versions < 2.1.16)
4. Is there a fix for CVE-2022-31034? Yes. CVE-2022-31034 is fixed in 2.1.16, 2.2.10, 2.3.5, 2.4.1. Upgrade to this version or later.
5. Is CVE-2022-31034 exploitable, and should I be worried? Whether CVE-2022-31034 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-31034 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-31034?
   • Upgrade github.com/argoproj/argo-cd to 2.1.16 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.1.16 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.2.10 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.3.5 or later
   • Upgrade github.com/argoproj/argo-cd/v2 to 2.4.1 or later