Kubernetes kube-apiserver allows access to custom resources via wrong scope
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2019-11247
Credits & Attribution
The following person or organization is credited with identifying this vulnerability, as recorded in the NVD database:
- Prabu Shyam, Verizon Media
References
- https://github.com/kubernetes/kubernetes/issues/80983
- https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJ
- https://access.redhat.com/errata/RHSA-2019:2690
- https://security.netapp.com/advisory/ntap-20190919-0003/
- https://access.redhat.com/errata/RHBA-2019:2816
- https://access.redhat.com/errata/RHBA-2019:2824
- https://access.redhat.com/errata/RHSA-2019:2769
More from Kubernetes
View All →Affected Vendor
Kubernetes
View all reports →