temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases replace the message and clear the stack trace of every outbound failure that carries encoded attributes, in any encoding, whenever the proxy is configured with encryption keys, whether or not encryption.failures is set. A custom failure converter that sends readable text beside its own encoded attributes will find that text replaced at the upstream. Upgrading does not re-encrypt failure text the upstream already stores. Releases before 1.0.0 receive no fix.
Vendor Workaround
No proxy setting closes this issue: with encryption.failures off, the proxy still restores failure text that the SDK encoded, and a Worker that sends it back still sends it in plaintext. Until a fixed release is deployed, keep sensitive data out of failure messages and stack traces.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
No data.
No data.
No data.
No data.
No data.