WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
- 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 4.0.2, 3.7.11
- 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: poc
- Automatable: no
- Technical impact: total
Summary
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- argoproj argo-workflows
From 4.0.0 · fixed in 4.0.2; From 2.9.0 · fixed in 3.7.11
- github.com/argoproj/argo-workflowsGo
All versions
- github.com/argoproj/argo-workflows/v2Go
From 2.9.0
- github.com/argoproj/argo-workflows/v3Go
fixed in 3.7.11
- github.com/argoproj/argo-workflows/v4Go
fixed in 4.0.2
- github.com/argoproj/argo-workflowsGo
From 2.9.0