CVE-2019-11247
published 2019-08-29CVE-2019-11247: The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced…
PriorityP350high8.1CVSS 3.1
AVNACLPRLUINSUCHIHAN
EPSS
2.09%
79.5th percentile
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
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | kubernetes | < kubernetes 1.17.4-1 (bookworm) | kubernetes 1.17.4-1 (bookworm) |
| k8s.io | apiextensions-apiserver | >= 0.14.0 < 0.14.5 | 0.14.5 |
| k8s.io | apiextensions-apiserver | >= 0.15.0 < 0.15.2 | 0.15.2 |
| k8s.io | apiextensions-apiserver | >= 0.7.0 < 0.13.9 | 0.13.9 |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | — | — |
| kubernetes | kubernetes | >= 0 < 1.17.4-1 | 1.17.4-1 |
| kubernetes | kubernetes | >= 0 < 1.17.4-1 | 1.17.4-1 |
| kubernetes | kubernetes | >= 0 < 1.17.4-1 | 1.17.4-1 |
| kubernetes | kubernetes | >= 0 < 1.17.4-1 | 1.17.4-1 |
| kubernetes | kubernetes | >= 1.13.0 < 1.13.9 | 1.13.9 |
| kubernetes | kubernetes | >= 1.14.0 < 1.14.5 | 1.14.5 |
| kubernetes | kubernetes | >= 1.15.0 < 1.15.2 | 1.15.2 |
| kubernetes | kubernetes | 1.7.0 – 1.12.10 | — |
| redhat | openshift_container_platform | — | — |
| redhat | openshift_container_platform | — | — |
| redhat | openshift_container_platform | — | — |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvdv3.05.0MEDIUMCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
nvdv2.06.5MEDIUMAV:N/AC:L/Au:S/C:P/I:P/A:P
osv8.1HIGH
vendor_debian8.1HIGH
vendor_redhat8.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
vendor_redhat·2019-08-05·CVSS 8.1
CVE-2019-11247 [HIGH] CWE-284 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
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.
Package: heketi (Red Hat Storage 3) - Not affected
Debian
CVE-2019-11247: kubernetes - The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custo...
vendor_debian·2019·CVSS 8.1
CVE-2019-11247 [HIGH] CVE-2019-11247: kubernetes - The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custo...
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.
Scope: local
bookworm: resolved (fixed in 1.17.4-1)
bullseye: resolved (fixed in 1.17.4-1)
forky: resolved (fixed in 1.17.4-1)
sid: resolved (fixed in 1.17.4-1)
trixie: resolved (fixed in
GHSA
Kubernetes kube-apiserver unauthorized access
ghsa·2022-05-24
CVE-2019-11247 [HIGH] CWE-863 Kubernetes kube-apiserver unauthorized access
Kubernetes kube-apiserver unauthorized access
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.
OSV
Kubernetes kube-apiserver unauthorized access
osv·2022-05-24
CVE-2019-11247 [HIGH] Kubernetes kube-apiserver unauthorized access
Kubernetes kube-apiserver unauthorized access
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.
OSV
CVE-2019-11247: The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced
osv·2019-08-29·CVSS 8.1
CVE-2019-11247 [HIGH] CVE-2019-11247: The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced [fedora-all]
bugzilla·2019-08-05·CVSS 8.1
CVE-2019-11247 [HIGH] CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced [fedora-all]
CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Bugzilla
CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
bugzilla·2019-07-23·CVSS 8.1
CVE-2019-11247 [HIGH] CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
CVE-2019-11247 kubernetes: API server allows access to cluster-scoped custom resources as if resources were namespaced
The Kubernetes API server 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).
Discussion:
Acknowledgments:
Name: the Kubernetes Product Security Committee
---
Upstream Issue:
https://github.com/kubernetes/kubernetes/issues/80983
---
External References:
https://groups.google.com/forum/#!topic/kubernet
https://access.redhat.com/errata/RHBA-2019:2816https://access.redhat.com/errata/RHBA-2019:2824https://access.redhat.com/errata/RHSA-2019:2690https://access.redhat.com/errata/RHSA-2019:2769https://github.com/kubernetes/kubernetes/issues/80983https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJhttps://security.netapp.com/advisory/ntap-20190919-0003/https://access.redhat.com/errata/RHBA-2019:2816https://access.redhat.com/errata/RHBA-2019:2824https://access.redhat.com/errata/RHSA-2019:2690https://access.redhat.com/errata/RHSA-2019:2769https://github.com/kubernetes/kubernetes/issues/80983https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJhttps://security.netapp.com/advisory/ntap-20190919-0003/
2019-08-29
Published