Unauthorized read of Custom Resources
- 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 1.22.16, 1.23.14, 1.24.8, 1.25.4
- 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
Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Kubernetes Kubernetes
through v1.25.3; through v1.24.7; through v1.23.13; through v1.22.15
- k8s.io/kubernetesGo
From 1.22.0 · fixed in 1.22.16; From 1.23.0 · fixed in 1.23.14; From 1.24.0 · fixed in 1.24.8; From 1.25.0 · fixed in 1.25.4
- github.com/kubernetes/kubernetesGo
From 1.25.0 · fixed in 1.25.4
- github.com/kubernetes/kubernetesGo
From 1.24.0 · fixed in 1.24.8
- github.com/kubernetes/kubernetesGo
From 1.23.0 · fixed in 1.23.14
- github.com/kubernetes/kubernetesGo
From 1.22.0 · fixed in 1.22.16