temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address
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.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.
Vendor Workaround
Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.
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.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line. | |
| Title | temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address | |
| Weaknesses | CWE-488 | |
| References |
|
|
| Metrics |
cvssV4_0
|
No data.
No data.
No data.
No data.
No data.