Argo Workflows has unauthorized access to Argo Workflows Template
argoproj argo-workflows
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows/v4 Go |
|
|
argoproj argo-workflows
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows/v4 Go |
|
|
| github.com/argoproj/argo-workflows Go |
|
| No fix yet |
| github.com/argoproj/argo-workflows/v2 Go |
| No fix yet |
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 4.0.2 and 3.7.11, Workflow templates endpoints allow any client to retrieve WorkflowTemplates (and ClusterWorkflowTemplates). Any request with a Authorization: Bearer nothing token can leak sensitive template content, including embedded Secret manifests. This vulnerability is fixed in 4.0.2 and 3.7.11.
From the CVE record · GitHub_M
Workflow template endpoints in affected Argo Workflows versions allow any client to retrieve WorkflowTemplates and ClusterWorkflowTemplates by sending an Authorization header with a `Bearer nothing` token. The response can expose sensitive template content, including embedded Secret manifests, without valid authentication or user interaction.
Operators of Argo Workflows before 3.7.11 or 4.0.2, and users of the unversioned or v2 Go packages, should check their deployments.