ExecuteMultiOperation Namespace Policy Bypass
- 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 1.27.4, 1.28.2, 1.29.2
- 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: yes
- Technical impact: partial
Summary
When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- temporal
From 1.24.0 · through 1.29.1; From 1.24.0 · through 1.28.1; From 1.24.0 · through 1.27.3
- go.temporal.io/serverGo
From 1.24.0 · fixed in 1.27.4
- go.temporal.io/serverGo
From 1.28.0 · fixed in 1.28.2
- go.temporal.io/serverGo
From 1.29.0 · fixed in 1.29.2
- go.temporal.io/serverGo
From 1.24.0 · fixed in 1.27.4; From 1.28.0 · fixed in 1.28.2; From 1.29.0 · fixed in 1.29.2