CVE-2022-31034
published 2022-06-27CVE-2022-31034: 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…
PriorityP345high8.1CVSS 3.1
AVNACHPRNUINSUCHIHAH
EPSS
0.89%
54.8th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo_cd | — | — |
| argoproj | argo_cd | — | — |
| argoproj | argo_cd | — | — |
| argoproj | argo_cd | >= 0.11.0 < 2.1.16 | 2.1.16 |
| github.com | argoproj_argo-cd | >= 0.11.0 < 2.1.16 | 2.1.16 |
| github.com | argoproj_argo-cd | >= 0.11.0 | — |
| github.com | argoproj_argo-cd_v2 | >= 0 < 2.1.16 | 2.1.16 |
| github.com | argoproj_argo-cd_v2 | >= 2.2.0 < 2.2.10 | 2.2.10 |
| github.com | argoproj_argo-cd_v2 | >= 2.3.0 < 2.3.5 | 2.3.5 |
| github.com | argoproj_argo-cd_v2 | >= 2.4.0 < 2.4.1 | 2.4.1 |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
vendor_redhat8.3HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params in github.com/argoproj/argo-cd
osv·2024-08-21
CVE-2022-31034 Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params in github.com/argoproj/argo-cd
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params in github.com/argoproj/argo-cd
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params in github.com/argoproj/argo-cd
GHSA
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
ghsa·2022-06-21
CVE-2022-31034 [HIGH] CWE-330 Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
### Impact
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 accompli
OSV
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
osv·2022-06-21
CVE-2022-31034 [HIGH] Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params
### Impact
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 accompli
Red Hat
argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI.
vendor_redhat·2022-06-15·CVSS 8.3
CVE-2022-31034 [HIGH] CWE-331 argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI.
argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI.
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 b
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4vhttps://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v
2022-06-27
Published