CVE-2019-11247 is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in k8s.io/apiextensions-apiserver. A fix is available for k8s.io/apiextensions-apiserver — see the affected versions and patch details below.
Kubernetes kube-apiserver unauthorized access
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
k8s.io/apiextensions-apiserver🐹k8s.io/apiextensions-apiserver🐹k8s.io/apiextensions-apiserverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.7.0&&< 0.13.9 | 0.13.9go get k8s.io/apiextensions-apiserver@v0.13.9 |
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.14.0&&< 0.14.5 | 0.14.5go get k8s.io/apiextensions-apiserver@v0.14.5 |
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.15.0&&< 0.15.2 | 0.15.2go get k8s.io/apiextensions-apiserver@v0.15.2 |
Affected Products
kuberneteskubernetesopenshift container platformredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/apiextensions-apiserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update k8s.io/apiextensions-apiserver to 0.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11247 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift-0:3.10.170-1.git.0.8e592d6.el7 | RHSA-2019:2690 |
| Red Hat OpenShift Container Platform 3.11 | ansible-service-broker-1:1.3.23-2.el7 | RHBA-2019:2816 |
| Red Hat OpenShift Container Platform 3.9 | ansible-service-broker-0:1.1.20-2.el7 | RHSA-2019:2769 |
| Red Hat OpenShift Container Platform 4.1 | openshift-0:4.1.10-201908060758.git.0.d81afa6.el7 | RHSA-2019:2504 |
Frequently Asked Questions
Is CVE-2019-11247 in your dependencies?
Find it across Go, including transitive dependencies.