Vulnerabilities · 2019 · Kubernetes
CVE-2019-11247
Kubernetes vulnerability
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.
Affected products
Kubernetes, Openshift Container Platform. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Kubernetes runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/errata/RHBA-2019:2816 · Third Party Advisory
- access.redhat.com/errata/RHBA-2019:2824 · Third Party Advisory
- access.redhat.com/errata/RHSA-2019:2690 · Third Party Advisory
- access.redhat.com/errata/RHSA-2019:2769 · Third Party Advisory
- github.com/kubernetes/kubernetes/issues/80983 · Third Party Advisory
- groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJ · Third Party Advisory
- security.netapp.com/advisory/ntap-20190919-0003/ · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-11247
- cve.org/CVERecord?id=CVE-2019-11247
More vulnerabilities in Kubernetes products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.