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.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHBA-2019:2816 | Third Party Advisory |
https://access.redhat.com/errata/RHBA-2019:2824 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2690 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2769 | Third Party Advisory |
https://github.com/kubernetes/kubernetes/issues/80983 | Third Party Advisory |
https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJ | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20190919-0003/ | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: kubernetes
Published: 2019-08-05T00:00:00
Updated: 2019-10-24T22:06:25
Reserved: 2019-04-17T00:00:00
Link: CVE-2019-11247
JSON object: View
NVD Information
Status : Analyzed
Published: 2019-08-29T01:15:11.287
Modified: 2020-10-02T16:21:57.087
Link: CVE-2019-11247
JSON object: View
Redhat Information
No data.