Kubernetes operator resource-scope enforcement fixed
highHTTPEndpoint, MCPServer, or Configuration resources when untrusted workloads share a namespaceAny Dapr-enabled pod in a Kubernetes namespace could use direct operator access with a workload identity for an app ID in that namespace to read other apps’ scoped resources, including values stored in Kubernetes secrets. The operator now checks scopes before resolving secrets, returns out-of-scope resiliency resources as not found, and limits GetConfiguration to the config named by the calling pod’s dapr.io/config annotation; daprd without the injector using --config must run in a pod with the specified enabled, app-ID, and config annotations, the app-ID label, and a daprd container.
Show release-note lines
In Kubernetes mode, the Dapr operator returned HTTPEndpoint and MCPServer resources to every Dapr-enabled pod in the namespace, with their Kubernetes secret references resolved to plaintext, regardless of the resources' `scopes`. `GetConfiguration` returned any Configuration in the namespace by name, with secret OpenTelemetry headers resolved. `ListResiliency`, `GetResiliency`, `ListSubscriptions` and `ListWorkflowAccessPolicy` also ignored `scopes`, although they carry no secrets. Any workload that can obtain a Dapr workload identity for an app ID in a namespace, which includes every Dapr-enabled pod in that namespace, could call the operator directly and read: Only values stored in the Kubernetes secret store (the default) were disclosed, because the operator resolves only those. Resources in other namespaces were not exposed. Sidecars already ignored resources not scoped to their app ID, so applications behaved correctly; the problem was what the operator sent to them. If untrusted workloads share a namespace with scoped HTTPEndpoint, MCPServer or Configuration resources, rotate the Kubernetes secrets those resources reference. The operator now skips resources whose `scopes` do not include the calling app ID before resolving any secret, and `GetResiliency` reports them as not found. `GetConfiguration` only serves the configuration named in the `dapr.io/config` annotation of one of the calling app's pods. A daprd run in Kubernetes mode without the injector, with `--config`, must now be in a pod with the `dapr.io/enabled: "true"`, `dapr.io/app-id` and `dapr.io/config` annotations and the `dapr.io/app-id` label, and its container must be named `daprd`.github.com/dapr/dapr/security/advisories/GHSA-99h8-29cw-6j59
Users running Dapr on Kubernetes are encouraged to upgrade to `1.19.0`, `1.18.9` or `1.17.18`.github.com/dapr/dapr/security/advisories/GHSA-99h8-29cw-6j59