Denial of Service if invalid UTF-8 sent
- 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.20.5, 1.21.6, 1.22.7
- 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: no
- Technical impact: partial
Summary
Denial of Service in Temporal Server prior to version 1.20.5, 1.21.6, and 1.22.7 allows an authenticated user who has permissions to interact with workflows and has crafted an invalid UTF-8 string for submission to potentially cause a crashloop. If left unchecked, the task containing the invalid UTF-8 will become stuck in the queue, causing an increase in queue lag. Eventually, all processes handling these queues will become stuck and the system will run out of resources. The workflow ID of the failing task will be visible in the logs, and can be used to remove that workflow as a mitigation. Version 1.23 is not impacted. In this context, a user is an operator of Temporal Server.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- temporalio/server
fixed in 1.20.5; From 1.21.0 · fixed in 1.21.6; From 1.22.0 · fixed in 1.22.7
- go.temporal.io/serverGo
fixed in 1.20.5; From 1.21.0 · fixed in 1.21.6; From 1.22.0-rc1 · fixed in 1.22.7
- github.com/temporalio/temporalGo
From 1.22.0-rc1 · fixed in 1.22.7
- github.com/temporalio/temporalGo
From 1.21.0 · fixed in 1.21.6
- github.com/temporalio/temporalGo
fixed in 1.20.5