etcd: Watch API authorization bypass via open-ended range requests
etcd-io etcd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd/server/v3 Go |
etcd-io etcd
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd/server/v3 Go |
< 3.5.33≥ 3.6.0 · < 3.6.14≥ 3.7.0-alpha.0 · < 3.7.1
|
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.5.33, 3.6.14, and 3.7.1, a user granted READ permission on a single exact key can use the Watch gRPC API with clientv3.WithFromKey() to receive watch events for every key lexicographically greater than or equal to the permitted key. In server/etcdserver/api/v3rpc/watch.go, the open-ended RangeEnd sentinel is rewritten before the RBAC permission check in server/auth/range_perm_cache.go function isRangeOpPermitted, causing the request to be treated as an exact-key watch. Range/Get and DeleteRange requests are not affected, and the issue affects only clusters with authentication enabled. This issue is fixed in versions 3.5.33, 3.6.14, and 3.7.1.
From the CVE record · GitHub_M
In etcd clusters with authentication enabled, a user with READ permission on one exact key can use the Watch gRPC API to receive events for that key and every lexicographically greater key. Range/Get and DeleteRange requests are not affected; no user interaction is required.
Operators of etcd and users of go.etcd.io/etcd/v3 or go.etcd.io/etcd/server/v3 should check versions below 3.5.33, from 3.6.0 to before 3.6.14, or from 3.7.0-alpha.0 to before 3.7.1.