Kubernetes kube-apiserver allows access to custom resources via wrong scope
- 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 0.13.9, 0.14.5, 0.15.2
- 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
Summary
The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes Kubernetes
prior to 1.13.9, prior to 1.14.5, prior to 1.15.2, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12
- k8s.io/apiextensions-apiserverGo
From 0.7.0 · fixed in 0.13.9
- k8s.io/apiextensions-apiserverGo
From 0.14.0 · fixed in 0.14.5
- k8s.io/apiextensions-apiserverGo
From 0.15.0 · fixed in 0.15.2