Kubernetes kube-apiserver allows access to custom resources via wrong scope
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/apiextensions-apiserver Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/apiextensions-apiserver Go |
|
|
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.
From the CVE record · kubernetes
Kubernetes kube-apiserver can mistakenly treat a request for a cluster-scoped custom resource as namespaced and apply namespace role permissions. A user with access to the resource in a namespace can then create, view, update, or delete the cluster-scoped resource, depending on those permissions. The issue requires namespace-level access; no user interaction is described.
Check Kubernetes installations running versions 1.7–1.12, versions before 1.13.9, 1.14.5, or 1.15.2 in their respective release lines, and Go k8s.io/apiextensions-apiserver packages in the listed affected ranges.