Cross Namespace Commands Authorization Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Temporal | Temporal | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Temporal | Temporal | — |
Vendor Workaround
Set system.enableCrossNamespaceCommands to false, unless cross-namespace workflow-task commands are explicitly required.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hmhp-gh8m-c8xp | Temporal has an Incorrect Authorization vulnerability |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.401% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Temporal
Temporal temporal |
|
| Vendors & Products |
Temporal
Temporal temporal |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When system.enableCrossNamespaceCommands is enabled (on by default), the Temporal server permits certain workflow task commands (e.g. StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) to target a different namespace than the namespace authorized at the gRPC boundary. The frontend authorizes RespondWorkflowTaskCompleted based on the outer request namespace, but the history service later resolves and executes the command using the namespace embedded in command attributes without authorizing the caller for that target namespace. This can allow a worker authorized for one namespace to create, signal, or cancel workflows in another namespace. This issue affects Temporal: through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2. | |
| Title | Cross Namespace Commands Authorization Bypass | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV4_0
|