GHSA-M3M4-54F5-4WJ2
Server: Archived Workflow names are enumerable via `GET`, `DELETE`, resubmit, and retry
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-M3M4-54F5-4WJ2 divulgada · CVSS 4.3 (GitHub) | |
| Remediación | Parche v4.0.12 | github.com/argoproj/argo-workflows/v4 · 0 d desde divulgación | |
| Remediación | Parche v4.1.4 | github.com/argoproj/argo-workflows/v4 · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The `GET` method for individual archived workflows will return a 404 https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L108 if a Workflow is not found with no authorization. Authorization is only performed a few lines down, after verifying that the Workflow exists. So existing Workflows will return a 403 (`PermissionDenied`), while non-existent ones return a 404.
This difference allows an attacker to enumerate all Workflows by name, even if they do not have RBAC to `get` those.
Details
The 404 return https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L108 in the `GET` method should occur _after_ authorization. i.e. the `kubectl auth can-i` check https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L110 should occur first.
- This also impacts `DELETE` as it calls `GetArchivedWorkflow` and returns the original error
https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L123wrapped in a 500 - Same with Resubmit
https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L196and Retryhttps://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L217
This dates back to https://github.com/argoproj/argo-workflows/pull/1882 / v2.5.0-rc1; this has existed as long as the Server has existed.
### PoC
Using a token that has no RBAC on Workflows in namespace `other-ns`, request an archived Workflow by name through the resubmit endpoint. The `uid` path segment is ignored when `name` is set in the body; the same applies to `retry`, and to `GET` and `DELETE` when called over gRPC with `name` and `namespace`.
curl -s -o /dev/null -w '%{http_code}\n' -X PUT "https://localhost:2746/api/v1/archived-workflows/x/resubmit" \
-H "Authorization: $ARGO_TOKEN" -d '{"namespace":"other-ns","name":"does-not-exist"}'
# 404
curl -s -o /dev/null -w '%{http_code}\n' -X PUT "https://localhost:2746/api/v1/archived-workflows/x/resubmit" \
-H "Authorization: $ARGO_TOKEN" -d '{"namespace":"other-ns","name":"real-workflow-name"}'
# 403The 404 is returned before any authorization check, so the difference reveals whether `real-workflow-name` exists in the archive.
Patches
Fixed in v4.1.4 and v4.0.12. `GetArchivedWorkflow` now performs the `get` authorization check before answering, using the requested namespace and name when no Workflow was found, so a caller without permission receives `permission denied` whether or not the Workflow exists. `DELETE`, resubmit and retry call `GetArchivedWorkflow` and inherit the fix.
v3 is not being patched. Users on v3 should upgrade.
Workarounds
None beyond restricting who can reach the Server.
Impact
This allows an attacker to enumerate all Workflows by name.
This is potentially useful information, especially if the names have semantic significance. Otherwise, this is a low impact information disclosure as the name on its own is often not very useful.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/argoproj/argo-workflows/v4 |
Corregida | v4.0.12, v4.1.4 | 0 d · 0 d | v4.1.6 no afectada |
gogithub.com/argoproj/argo-workflows/v3 |
Sin parche | — | — | v3.7.18 afectada |
4.0.12v4.0.124.1.4v4.1.4Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/argoproj/argo-workflows/security/advisories/GHSA-m3m4-54f5-4wj2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
