# CVE-2022-31034: Insecure entropy in argo-cd > Insufficient entropy in OAuth2/OIDC parameters allows attackers to potentially gain admin access to Argo CD. - **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **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:** Yes - **Published:** 27 Jun 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-2m7h-86qq-fp4v, GO-2022-0497 ## 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. Weakness: CWE-331 (Insufficient Entropy), CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)), CWE-330 (Use of Insufficiently Random Values) ## 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 | Ecosystem | 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 | | `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: 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](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-31034 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2022-31034 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16, 2.2.10, 2.3.5, 2.4.1 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.1.16 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.2.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.2.0; fixed in 2.2.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.3.0; fixed in 2.3.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.3.0; fixed in 2.3.5 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.4.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.4.0; fixed in 2.4.1 - github.com/argoproj/argo-cd (Go): affected from 0.11.0; no fix listed - github.com/argoproj/argo-cd (Go): affected from 0.11.0; fixed in 2.1.16 - github.com/argoproj/argo-cd (Go): affected from 0.11.0; fixed in 2.1.16 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-31034/ (Markdown: https://insights.sbomify.com/CVE-2022-31034/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31034 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31034 - OSV: https://osv.dev/vulnerability/CVE-2022-31034 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-31034/ Summaries are generated and may contain mistakes; the official description above is the record.