A connected peer cluster can modify a Temporal Server cluster's local namespaces, which are never…

Why it is Yellow

• CVSS 7.0 high

References

• https://github.com/temporalio/temporal/blob/v1.0.0/common/namespace/replicationTaskExecutor.go#L191-L260
• https://github.com/temporalio/temporal/commit/f2b571e2eee8a9143fbc4711f3db8b5a37146b3b
• https://github.com/temporalio/temporal/pull/12323
• https://github.com/temporalio/temporal/pull/12328
• https://github.com/temporalio/temporal/pull/12329
• https://github.com/temporalio/temporal/pull/12330
• https://github.com/temporalio/temporal/releases/tag/v1.30.8
• https://github.com/temporalio/temporal/releases/tag/v1.31.4
• https://github.com/temporalio/temporal/releases/tag/v1.32.1

Original description

A connected peer cluster can modify a Temporal Server cluster's local namespaces, which are never replicated to that peer, because the receiving cluster applies inbound namespace replication updates to them. In a multi-cluster deployment, each cluster pulls replication tasks from the remote clusters an administrator has registered with connection enabled; the sending side excludes local namespaces, but the receiving side does not apply the same rule. When an inbound task names an existing namespace, the server checks at most that the namespace identifiers match, then overwrites its state, description, owner, retention, archival settings, and cluster list, and its active cluster when the task carries a higher failover version, without checking that the namespace is global. A party that controls a registered peer's replies, by operating or compromising it, can therefore change any local namespace whose name and identifier it can supply, without any credential on the receiving cluster: for example, marking it Deprecated, making the peer its active cluster, and shortening its retention, after which new Workflow starts in that namespace fail. Local namespaces include the built-in temporal-system namespace. Namespace metadata the History service refreshes from the peer while processing its history replication tasks passes through the same logic. A cluster with no remote cluster registered with connection enabled is not exposed.