CVE-2022-31034 Insecure entropy in argo-cd
Insufficient entropy in OAuth2/OIDC parameters allows attackers to potentially gain admin access to Argo CD.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-31034?
CVE-2022-31034 is a high-severity vulnerability in Argoproj Argo Cd, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. 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 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. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. There are no known workarounds for this vulnerability.
Which versions are affected by CVE-2022-31034?
12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16, 2.2.10, 2.3.5, 2.4.1 |
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16 |
github.com/argoproj/argo-cd/v2 Go | All versions | 2.1.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.2.0 | 2.2.10 |
github.com/argoproj/argo-cd/v2 Go | From 2.2.0 | 2.2.10 |
github.com/argoproj/argo-cd/v2 Go | From 2.3.0 | 2.3.5 |
6 more packages
github.com/argoproj/argo-cd/v2 Go | From 2.3.0 | 2.3.5 |
github.com/argoproj/argo-cd/v2 Go | From 2.4.0 | 2.4.1 |
github.com/argoproj/argo-cd/v2 Go | From 2.4.0 | 2.4.1 |
github.com/argoproj/argo-cd Go | From 0.11.0 | None |
github.com/argoproj/argo-cd Go | From 0.11.0 | 2.1.16 |
github.com/argoproj/argo-cd Go | From 0.11.0 | 2.1.16 |
Products include Argoproj Argo Cd.
How do I fix CVE-2022-31034?
Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.1.16, 2.2.10, 2.3.5 or 2.4.1.
Is CVE-2022-31034 being exploited?
There is no known exploitation of CVE-2022-31034 in the wild and no public exploit code.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
Sources
Also known as GHSA-2m7h-86qq-fp4v, GO-2022-0497.