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. 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-1243US | —OT elevated | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/temporalio/api-goPACKAGE
- https://github.com/temporalio/api-go/commit/dad8b169ada911d3778e070484d1ae78a58bd22bWEB
- https://github.com/temporalio/api-go/releases/tag/v1.44.1WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-1243ADVISORY
- https://temporal.io/blog/announcing-a-new-operation-workflow-updateWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan