Argo Workflows exposes artifact repository credentials in workflow-controller logs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.7.3, 3.6.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- argoproj argo-workflows
From 3.7.0 · fixed in 3.7.3; fixed in 3.6.12
- github.com/argoproj/argo-workflows/v3Go
From 3.7.0 · fixed in 3.7.3
- github.com/argoproj/argo-workflows/v3Go
fixed in 3.6.12
- github.com/argoproj/argo-workflowsGo
All versions
- github.com/argoproj/argo-workflows/v2Go
All versions
- github.com/argoproj/argo-workflows/v3Go
fixed in 3.6.12; From 3.7.0 · fixed in 3.7.3