| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/argoproj/argo-cd | all versions | |
| github.com/argoproj/argo-cd/v2 | ≥ 2.13.0, < 2.13.9≥ 2.14.0, < 2.14.16 | 2.13.92.14.16 |
| github.com/argoproj/argo-cd/v3 | ≥ 3.1.0-rc1, < 3.1.2< 3.0.14 | 3.1.23.0.14 |
| argo cd | ≥ 2.14.0, < 2.14.16≥ 2.2.0, < 2.13.9≥ 3.0.0, < 3.0.14≥ 3.1.0, < 3.1.2 | 2.14.162.13.93.0.143.1.2 |
Argo CD 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.
Component: Project API (/api/v1/projects/{project}/detailed)
API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets.
API tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.
Note: 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
p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow
p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow
p, proj:myProject:project-automation-role, applications, get, myProject/*, allow
bashcurl -sH "Authorization: Bearer $ARGOCD_API_TOKEN" \
"https://argocd.example.com/api/v1/projects/myProject/detailed"
{
"repositories": [
{
"username": "<REDACTED>",
"password": "<REDACTED>",
"type": "helm",
"name": "test-helm-repo",
"project": "myProject"
}
]
}
Credits to @ashishgoyal111 for helping identify this issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free