Argo Workflows affected by stored XSS in the artifact directory listing
argoproj argo-workflows
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows Go |
|
argoproj argo-workflows
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 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 versions 3.6.17 and 3.7.8, stored XSS in the artifact directory listing allows any workflow author to execute arbitrary JavaScript in another user’s browser under the Argo Server origin, enabling API actions with the victim’s privileges. Versions 3.6.17 and 3.7.8 fix the issue.
From the CVE record · GitHub_M
The artifact directory listing in Argo Workflows is vulnerable to stored cross-site scripting. A workflow author can cause JavaScript to run in another user’s browser under the Argo Server origin when that user views the listing, enabling API actions with the viewer’s privileges.
Teams running github.com/argoproj/argo-workflows/v3 before 3.6.17 or from 3.7.0 through 3.7.7, or running the legacy github.com/argoproj/argo-workflows or /v2 Go packages, should check their deployments.