gsd-2022-31034
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
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.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2022-31034", "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.", "id": "GSD-2022-31034", "references": [ "https://access.redhat.com/errata/RHSA-2022:5152", "https://access.redhat.com/errata/RHSA-2022:5187", "https://access.redhat.com/errata/RHSA-2022:5192", "https://access.redhat.com/errata/RHSA-2022:5153" ] }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2022-31034" ], "details": "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.", "id": "GSD-2022-31034", "modified": "2023-12-13T01:19:17.758289Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2022-31034", "STATE": "PUBLIC", "TITLE": "Insecure entropy in argo-cd" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "argo-cd", "version": { "version_data": [ { "version_value": "\u003e= 0.11.0, \u003c 2.1.16" }, { "version_value": "\u003e= 2.2.0, \u003c 2.2.10" }, { "version_value": "\u003e= 2.3.0, \u003c 2.3.5" }, { "version_value": "\u003e= 2.4.0, \u003c 2.4.1" } ] } } ] }, "vendor_name": "argoproj" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "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." } ] }, "impact": { "cvss": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 8.3, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H", "version": "3.1" } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-330: Use of Insufficiently Random Values" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v", "refsource": "CONFIRM", "url": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v" }, { "name": "https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0", "refsource": "MISC", "url": "https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0" } ] }, "source": { "advisory": "GHSA-2m7h-86qq-fp4v", "discovery": "UNKNOWN" } }, "gitlab.com": { "advisories": [ { "affected_range": "\u003e=v0.11.0 \u003c=v1.8.7", "affected_versions": "All versions starting from 0.11.0 up to 1.8.7", "cwe_ids": [ "CWE-1035", "CWE-937" ], "date": "2022-06-23", "description": "### Impact\n\nAll versions of Argo CD starting with v0.11.0 is 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.", "fixed_versions": [ "v2.1.16" ], "identifier": "GMS-2022-2554", "identifiers": [ "GHSA-2m7h-86qq-fp4v", "GMS-2022-2554", "CVE-2022-31034" ], "not_impacted": "All versions before 0.11.0, all versions after 1.8.7", "package_slug": "go/github.com/argoproj/argo-cd", "pubdate": "2022-06-21", "solution": "Upgrade to version 2.1.16 or above.", "title": "Insecure entropy in Argo CD\u0027s PKCE/Oauth2/OIDC params", "urls": [ "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v", "https://github.com/advisories/GHSA-2m7h-86qq-fp4v" ], "uuid": "454e5db0-cef8-4c50-81b8-eb9313f77e1b", "versions": [ { "commit": { "sha": "71b646dfaedfdbab9e83d314f1b76287561a18e1", "tags": [ "v0.11.0" ], "timestamp": "20190110231421" }, "number": "v0.11.0" }, { "commit": { "sha": "eb3d1fb84b9b77cdffd70b14c4f949f1c64a9416", "tags": [ "v1.8.7" ], "timestamp": "20210303070237" }, "number": "v1.8.7" }, { "commit": { "sha": "903db5fe464032bd5a10bf32fe17639e76634c2a", "tags": [ "v2.1.16" ], "timestamp": "20220621161926" }, "number": "v2.1.16" } ] }, { "affected_range": "\u003cv2.1.16 || \u003e=v2.2.0 \u003cv2.2.10 || \u003e=v2.3.0 \u003cv2.3.5 || =v2.4.0", "affected_versions": "All versions before 2.1.16, all versions starting from 2.2.0 before 2.2.10, all versions starting from 2.3.0 before 2.3.5, version 2.4.0", "cwe_ids": [ "CWE-1035", "CWE-937" ], "date": "2022-06-23", "description": "All versions of Argo CD starting with v0.11.0 is 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.", "fixed_versions": [ "v2.1.16", "v2.2.10", "v2.3.5", "v2.4.1" ], "identifier": "GMS-2022-2558", "identifiers": [ "GHSA-2m7h-86qq-fp4v", "GMS-2022-2558", "CVE-2022-31034" ], "not_impacted": "All versions starting from 2.1.16 before 2.2.0, all versions starting from 2.2.10 before 2.3.0, all versions starting from 2.3.5 before 2.4.0, all versions after 2.4.0", "package_slug": "go/github.com/argoproj/argo-cd/v2", "pubdate": "2022-06-21", "solution": "Upgrade to versions 2.1.16, 2.2.10, 2.3.5, 2.4.1 or above.", "title": "Insecure entropy in Argo CD\u0027s PKCE/Oauth2/OIDC params", "urls": [ "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v", "https://github.com/advisories/GHSA-2m7h-86qq-fp4v" ], "uuid": "56b708be-4750-4ea9-ba85-e93df4c2b146", "versions": [ { "commit": { "sha": "6da92a8e8103ce4145bb0fe2b7e952be79c9ff0a", "tags": [ "v2.2.0" ], "timestamp": "20211214180104" }, "number": "v2.2.0" }, { "commit": { "sha": "fe427802293b090f43f91f5839393174df6c3b3a", "tags": [ "v2.3.0" ], "timestamp": "20220306061859" }, "number": "v2.3.0" }, { "commit": { "sha": "91aefabc5b213a258ddcfe04b8e69bb4a2dd2566", "tags": [ "stable", "v2.4.0" ], "timestamp": "20220610171343" }, "number": "v2.4.0" }, { "commit": { "sha": "903db5fe464032bd5a10bf32fe17639e76634c2a", "tags": [ "v2.1.16" ], "timestamp": "20220621161926" }, "number": "v2.1.16" }, { "commit": { "sha": "8db0e57b738ff5b0b276031573576fdc3498c04f", "tags": [ "v2.2.10" ], "timestamp": "20220621162737" }, "number": "v2.2.10" }, { "commit": { "sha": "52e6025f8b565705025d029e8bed36d6caa5ecf7", "tags": [ "v2.4.1" ], "timestamp": "20220621162747" }, "number": "v2.4.1" }, { "commit": { "sha": "1287d24bfe47bcaa6e791e5ff12fa1c1bf57a442", "tags": [ "v2.3.5" ], "timestamp": "20220621162823" }, "number": "v2.3.5" } ] } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo-cd:2.3.4:*:*:*:*:*:*:*", "cpe_name": [], "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo-cd:2.4.0:*:*:*:*:*:*:*", "cpe_name": [], "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo-cd:2.2.9:*:*:*:*:*:*:*", "cpe_name": [], "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo-cd:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "2.1.16", "versionStartIncluding": "0.11.0", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2022-31034" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-331" }, { "lang": "en", "value": "CWE-335" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0", "refsource": "MISC", "tags": [ "Patch", "Third Party Advisory" ], "url": "https://github.com/argoproj/argo-cd/commit/17f7f4f462bdb233e1b9b36f67099f41052d8cb0" }, { "name": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v", "refsource": "CONFIRM", "tags": [ "Third Party Advisory" ], "url": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v" } ] } }, "impact": { "baseMetricV2": { "acInsufInfo": false, "cvssV2": { "accessComplexity": "MEDIUM", "accessVector": "NETWORK", "authentication": "NONE", "availabilityImpact": "PARTIAL", "baseScore": 6.8, "confidentialityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "version": "2.0" }, "exploitabilityScore": 8.6, "impactScore": 6.4, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "severity": "MEDIUM", "userInteractionRequired": false }, "baseMetricV3": { "cvssV3": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 8.1, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" }, "exploitabilityScore": 2.2, "impactScore": 5.9 } }, "lastModifiedDate": "2023-07-21T17:09Z", "publishedDate": "2022-06-27T19:15Z" } } }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.