etcd: Nested etcd transactions bypass RBAC authorization checks
etcd-io etcd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
etcd-io etcd
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
≤ 3.3.27all versions| No fix yet |
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, an authenticated user with RBAC restricted permissions on key ranges can use nested transactions to bypass all key-level authorization. This allows any authenticated user with direct access to etcd to effectively ignore all key range restrictions, accessing the entire etcd data store. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
From the CVE record · GitHub_M
Affected etcd versions allow an authenticated user with direct access to etcd to use nested transactions to bypass RBAC key-range restrictions and access the entire data store. This requires authentication and direct access to etcd; no user interaction is described. Typical Kubernetes deployments are not affected because the API server handles authentication and authorization.
Operators using go.etcd.io/etcd/v3 before 3.4.42, from 3.5.0-alpha.0 to before 3.5.28, or from 3.6.0-alpha.0 to before 3.6.9, and users of the go.etcd.io/etcd package, should check their deployments.