Insecure Default Authorization in Temporal Server
Published Jun 30, 2023
3.6
LOWCVSS 3.1
EPSS 0.17%
Description
Insecure defaults in open-source Temporal Server before version 1.20 on all platforms allows an attacker to craft a task token with access to a namespace other than the one specified in the request. Creation of this task token must be done outside of the normal Temporal server flow. It requires the namespace UUID and information from the workflow history for the target namespace. Under these conditions, it is possible to interfere with pending tasks in other namespaces, such as marking a task failed or completed. If a task is targeted for completion by the attacker, the targeted namespace must also be using the same data converter configuration as the initial, valid, namespace for the task completion payload to be decoded by workers in the target namespace.
Affected products
-
Affected
- ≥ 1.9.1, < 1.20
Default status is the baseline for the product. Each version can override it (patched versions can be marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Temporal Technologies Inc. | Temporal Server | unaffected | Affected
|
No data.
No Red Hat product state for this CVE.
go.temporal.io/server
Go
Introduced 0 Fixed 1.20.0
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Go | go.temporal.io/server | 0 | 1.20.0 |
Remediation
Vendor solution
* Set frontend.enableTokenNamespaceEnforcement https://github.com/temporalio/temporal/pull/3798 to true * Upgrade to version 1.20 or above, where this is the default
References (4)
Change history (0)
No recorded changes yet.
CVE.org / MITRE
CISA Vulnrichment
Red Hat
No data
GitHub