← Übersicht Argo Workflows / Rollouts / Events

Server: Archived Workflow names are enumerable via `GET`, `DELETE`, resubmit, and retry

GHSA-m3m4-54f5-4wj2

Mittel · CVSS 4.3 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
18.09.2026 10:13
Zuletzt geändert
18.09.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### 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#L123) wrapped in a 500 - Same with [Resubmit](https://github.com/argoproj/argo-workflows/blob/ed3b8ce778c23e3b3c0d54f87f790e966b15fdb3/server/workflowarchive/archived_workflow_server.go#L196) and [Retry](https://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`. ```sh 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"}' # 403 ``` The 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.

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-workflows/v3kein Fix bekanntGHSA-m3m4-54f5-4wj2
Gogithub.com/argoproj/argo-workflows/v44.1.0 → 4.1.4GHSA-m3m4-54f5-4wj2
Gogithub.com/argoproj/argo-workflows/v44.0.0 → 4.0.12GHSA-m3m4-54f5-4wj2

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.