Hide Forgot
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 the 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.
This issue has been addressed in the following products: Red Hat OpenShift GitOps 1.5 Via RHSA-2022:5152 https://access.redhat.com/errata/RHSA-2022:5152
This issue has been addressed in the following products: Red Hat OpenShift GitOps 1.4 Via RHSA-2022:5153 https://access.redhat.com/errata/RHSA-2022:5153
This issue has been addressed in the following products: Red Hat OpenShift GitOps 1.3 Via RHSA-2022:5192 https://access.redhat.com/errata/RHSA-2022:5192
This issue has been addressed in the following products: Red Hat OpenShift GitOps 1.3 Via RHSA-2022:5187 https://access.redhat.com/errata/RHSA-2022:5187
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-31034