Kubernetes kube-apiserver unauthorized access
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-11247US | high8.1OT elevated | — | ||
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 resourc… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHBA-2019:2816WEB
- https://access.redhat.com/errata/RHBA-2019:2824WEB
- https://access.redhat.com/errata/RHSA-2019:2690WEB
- https://access.redhat.com/errata/RHSA-2019:2769WEB
- https://github.com/kubernetes/apiextensions-apiserverPACKAGE
- https://github.com/kubernetes/apiextensions-apiserver/commit/b9b7d2b3f32f8edbeb47b8726710eeb868bce196WEB
- https://github.com/kubernetes/kubernetes/issues/80983WEB
- https://github.com/kubernetes/kubernetes/pull/80750WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan