CVE-2025-1243: Unencrypted transmission in Temporal api-go library
The Temporal api-go library prior to version 1.44.1 did not send update response information to Data Converter when the proxy package within the api-go module was used in a gRPC proxy prior to transmission. This resulted in information contained within the update response field not having Data Converter transformations (e.g. encryption) applied.
Published Feb 12, 2025
Affected packages
go.temporal.io/api
- Ecosystem
- Go
- Affected
- < 1.44.1
- Fixed in
- 1.44.1
- Check
go list -m go.temporal.io/api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
The Temporal api-go library prior to version 1.44.1 did not send update response information to Data Converter when the proxy package within the api-go module was used in a gRPC proxy prior to transmission. This resulted in information contained within the update response field not having Data Converter transformations (e.g. encryption) applied. This is an issue only when using the UpdateWorkflowExecution APIs (released on 13th January 2025) with a proxy leveraging the api-go library before version 1.44.1.
Other data fields were correctly sent to Data Converter. This issue does not impact the Data Converter server. Data was encrypted in transit. Temporal Cloud services are not impacted.
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-1243
- https://github.com/temporalio/api-go/releases/tag/v1.44.1
- https://temporal.io/blog/announcing-a-new-operation-workflow-update
- https://github.com/temporalio/api-go/commit/dad8b169ada911d3778e070484d1ae78a58bd22b
- https://github.com/advisories/GHSA-q9w6-cwj4-gf4p
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
