Argo Workflows exposes artifact repository credentials in workflow-controller logs
argoproj argo-workflows
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows Go |
| No fix yet |
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. Argo Workflows versions prior to 3.6.12 and versions 3.7.0 through 3.7.2 expose artifact repository credentials in plaintext in workflow-controller pod logs. An attacker with permissions to read pod logs in a namespace running Argo Workflows can read the workflow-controller logs and obtain credentials to the artifact repository. Update to versions 3.6.12 or 3.7.3 to remediate the vulnerability. No known workarounds exist.
From the CVE record · GitHub_M
Affected Argo Workflows versions write artifact repository credentials in plaintext to workflow-controller pod logs. An attacker with permission to read pod logs in a namespace running Argo Workflows can obtain those credentials.
Operators running Argo Workflows before 3.6.12 or versions 3.7.0–3.7.2 should check their deployments; the unversioned and v2 Go packages are affected in all versions and have no fixed release.