Argo CD: Project API Token Exposes Repository Credentials
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd/v3 Go |
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd/v3 Go |
|
|
| github.com/argoproj/argo-cd Go |
| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. In versions 2.13.0 through 2.13.8, 2.14.0 through 2.14.15, 3.0.0 through 3.0.12 and 3.1.0-rc1 through 3.1.1, API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets. This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: `p, role/user, projects, get, *, allow`. This issue is fixed in versions 2.13.9, 2.14.16, 3.0.14 and 3.1.2.
From the CVE record · GitHub_M
Argo CD’s project details API can expose repository usernames and passwords to API tokens with permission to get projects, including tokens without explicit access to secrets. An attacker needs such a token; project-level or global project-get permissions are sufficient.
Check Argo CD deployments using affected v2 versions (2.13.0–2.13.8 or 2.14.0–2.14.15), v3 versions (before 3.0.14 or 3.1.0-rc1–3.1.1), or any version of the unversioned Go package github.com/argoproj/argo-cd.