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
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
21 Nov 2024, 04:20
Type | Values Removed | Values Added |
---|---|---|
References | () https://access.redhat.com/errata/RHBA-2019:2816 - Third Party Advisory | |
References | () https://access.redhat.com/errata/RHBA-2019:2824 - Third Party Advisory | |
References | () https://access.redhat.com/errata/RHSA-2019:2690 - Third Party Advisory | |
References | () https://access.redhat.com/errata/RHSA-2019:2769 - Third Party Advisory | |
References | () https://github.com/kubernetes/kubernetes/issues/80983 - Third Party Advisory | |
References | () https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJ - Third Party Advisory | |
References | () https://security.netapp.com/advisory/ntap-20190919-0003/ - Third Party Advisory |
Information
Published : 2019-08-29 01:15
Updated : 2024-11-21 04:20
NVD link : CVE-2019-11247
Mitre link : CVE-2019-11247
CVE.ORG link : CVE-2019-11247
JSON object : View
Products Affected
redhat
- openshift_container_platform
kubernetes
- kubernetes