CVE-2019-11247

High

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.

SeverityHigh
CVSS8.1
Exploit probability—
ProductKubernetes
PublishedAug 29, 2019
First seenAug 29, 2019

How to fix

Update
  • kubernetes kubernetes1.13.9, 1.14.5, 1.15.2 or later
  • k8s.io/apiextensions-apiserver0.13.9, 0.14.5, 0.15.2 or later

Affected products

ProductAffected versionsFixed in
kubernetes kubernetes1.7.0 ≤ v ≤ 1.12.10, 1.13.0 ≤ v < 1.13.9, 1.14.0 ≤ v < 1.14.5, 1.15.0 ≤ v < 1.15.2, 1.12.111.13.9, 1.14.5, 1.15.2
redhat openshift_container_platform3.9, 3.10, 3.11—
k8s.io/apiextensions-apiserverGo0.7.0 ≤ v < 0.13.9, 0.14.0 ≤ v < 0.14.5, 0.15.0 ≤ v < 0.15.20.13.9, 0.14.5, 0.15.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.