CVE-2023-22482
published 2023-01-26CVE-2023-22482: 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…
PriorityP353high8.8CVSS 3.1
AVNACLPRLUINSUCHIHAH
EPSS
0.88%
54.5th percentile
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.
Affected
17 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 | >= 1.8.2 < 2.3.14 | 2.3.14 |
| argoproj | argo_cd | >= 2.4.0 < 2.4.20 | 2.4.20 |
| argoproj | argo_cd | >= 2.5.0 < 2.5.8 | 2.5.8 |
| github.com | argoproj_argo-cd | >= 1.8.2 < 2.3.14 | 2.3.14 |
| github.com | argoproj_argo-cd | >= 1.8.2 | — |
| github.com | argoproj_argo-cd | >= 2.4.0 < 2.4.20 | 2.4.20 |
| github.com | argoproj_argo-cd | >= 2.5.0 < 2.5.8 | 2.5.8 |
| github.com | argoproj_argo-cd | >= 2.6.0-rc1 < 2.6.0-rc5 | 2.6.0-rc5 |
| github.com | argoproj_argo-cd_v2 | >= 0 < 2.3.14 | 2.3.14 |
| github.com | argoproj_argo-cd_v2 | >= 2.4.0 < 2.4.20 | 2.4.20 |
| github.com | argoproj_argo-cd_v2 | >= 2.5.0 < 2.5.8 | 2.5.8 |
| github.com | argoproj_argo-cd_v2 | >= 2.6.0-rc1 < 2.6.0-rc5 | 2.6.0-rc5 |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.0CRITICAL
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
JWT audience claim is not verified in github.com/argoproj/argo-cd
osv·2024-08-20
CVE-2023-22482 JWT audience claim is not verified in github.com/argoproj/argo-cd
JWT audience claim is not verified in github.com/argoproj/argo-cd
JWT audience claim is not verified in github.com/argoproj/argo-cd
GHSA
JWT audience claim is not verified
ghsa·2023-01-25
CVE-2023-22482 [CRITICAL] CWE-863 JWT audience claim is not verified
JWT audience claim is not verified
### Impact
All versions of Argo CD starting with v1.8.2 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
OSV
JWT audience claim is not verified
osv·2023-01-25
CVE-2023-22482 [CRITICAL] JWT audience claim is not verified
JWT audience claim is not verified
### Impact
All versions of Argo CD starting with v1.8.2 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
Red Hat
ArgoCD: JWT audience claim is not verified
vendor_redhat·2023-01-25·CVSS 9.0
CVE-2023-22482 [CRITICAL] ArgoCD: JWT audience claim is not verified
ArgoCD: JWT audience claim is not verified
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 fi
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2023-01-26
Published