{"id":"EUVD-2023-0532","revision":"dd9f5c77ff2a4ccb9b17153a975a2129","records":[{"revision":"dd9f5c77ff2a4ccb9b17153a975a2129","observedAt":"2026-10-28T18:52:18.383+00:00","statement":{"source":"euvd","id":"EUVD-2023-0532","aliases":["CVE-2023-22482","GHSA-q9hr-j4rf-8fjc"],"title":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions of Argo CD starting with v1.8.2 and prior to 2.3.13, 2.4.19, 2.5.6, and 2.6.0-rc-3  are vulnerable to an improper authorization bug causing the API to accept…","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions of Argo CD starting with v1.8.2 and prior to 2.3.13, 2.4.19, 2.5.6, and 2.6.0-rc-3  are vulnerable to an improper authorization bug causing the API to accept certain invalid tokens. OIDC providers include an `aud` (audience) claim in signed tokens. The value of that claim specifies the intended audience(s) of the token (i.e. the service or services which are meant to accept the token). Argo CD _does_ validate that the token was signed by Argo CD's configured OIDC provider. But Argo CD _does not_ validate the audience claim, so it will accept tokens that are not intended for Argo CD. If Argo CD's configured OIDC provider also serves other audiences (for example, a file storage service), then Argo CD will accept a token intended for one of those other audiences. Argo CD will grant the user privileges based on the token's `groups` claim, even though those groups were not intended to be used by Argo CD. This bug also increases the impact of a stolen token. If an attacker steals a valid token for a different audience, they can use it to access Argo CD. A patch for this vulnerability has been released in versions 2.6.0-rc3, 2.5.6, 2.4.19, and 2.3.13. There are no workarounds.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","score":9.1,"severity":null}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-q9hr-j4rf-8fjc"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-0532","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Jan 25, 2023, 6:25:15 PM","dateUpdated":"Mar 11, 2025, 1:30:49 PM"},"relatedAdvisories":[{"id":"RHSA-2023:0467","title":"Red Hat Security Advisory: Red Hat OpenShift GitOps security update","vulnerabilityIds":["CVE-2023-22482","CVE-2023-22736"]},{"id":"WID-SEC-W-2023-0201","title":"Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen","vulnerabilityIds":["CVE-2023-22736","CVE-2023-22482"]},{"id":"RHSA-2023:0468","title":"Red Hat Security Advisory: Red Hat OpenShift GitOps security update","vulnerabilityIds":["CVE-2023-22482"]},{"id":"RHSA-2023:0466","title":"Red Hat Security Advisory: Red Hat OpenShift GitOps security update","vulnerabilityIds":["CVE-2023-22482"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2023-0532","identifiers":["EUVD-2023-0532","CVE-2023-22482","GHSA-q9hr-j4rf-8fjc"]},"retained":false,"historicalAffected":[]}],"coverage":[]}