etcd: Watch API authorization bypass via open-ended range requests
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5.33, 3.6.14, 3.7.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- etcd-io etcd
fixed in 3.5.33; From 3.6.0 · fixed in 3.6.14; From 3.7.0-alpha.0 · fixed in 3.7.1
- go.etcd.io/etcd/server/v3Go
fixed in 3.5.33; From 3.6.0 · fixed in 3.6.14; From 3.7.0-alpha.0 · fixed in 3.7.1
- go.etcd.io/etcd/v3Go
From 3.7.0-alpha.0 · fixed in 3.7.1
- go.etcd.io/etcd/v3Go
From 3.6.0 · fixed in 3.6.14
- go.etcd.io/etcd/v3Go
fixed in 3.5.33