Cross-namespace task manipulation via unenforced token namespace
Published Jun 30, 2023 · Updated Oct 28, 2024
Incorrect authorization in Temporal Server before 1.20.0 allows attackers to alter pending tasks via crafted cross-namespace task tokens. The frontend left token namespace enforcement disabled by default, so a token namespace ID could differ from the request namespace without rejection. Exploitation requires an externally created token, the target namespace UUID, and workflow-history data; completing a task also requires matching data converters.
Summary
What happened
Incorrect authorization in Temporal Server before 1.20.0 allows attackers to alter pending tasks via crafted cross-namespace task tokens. The frontend left token namespace enforcement disabled by default, so a token namespace ID could differ from the request namespace without rejection. Exploitation requires an externally created token, the target namespace UUID, and workflow-history data; completing a task also requires matching data converters.
The record
- CVE
- CVE-2023-3485
- Published
- Jun 30, 2023
- Updated
- Oct 28, 2024
- Vendor
- Temporal Technologies
- Product
- Temporal Server
- Classifications
- CWE-1188, CWE-863, T1565.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 30, 2023CVE publishedPublication date reported by the CVE source.
- Oct 28, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.9.1 <1.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo