Incorrect Authorization Affecting kubeadm package, versions <0:1.12.10-1.0.10.el7
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ORACLE7-KUBEADM-2547403
- published 10 Apr 2022
- disclosed 29 Aug 2019
Introduced: 29 Aug 2019
CVE-2019-11247 Open this link in a new tabHow to fix?
Upgrade Oracle:7 kubeadm to version 0:1.12.10-1.0.10.el7 or higher.
This issue was patched in ELSA-2019-4816.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kubeadm package and not the kubeadm package as distributed by Oracle.
See How to fix? for Oracle:7 relevant fixed versions and status.
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
- https://linux.oracle.com/cve/CVE-2019-11247.html
- https://linux.oracle.com/errata/ELSA-2019-4816.html
- https://github.com/kubernetes/kubernetes/issues/80983
- https://groups.google.com/d/msg/kubernetes-security-announce/vUtEcSEY6SM/v2ZZxsmtFQAJ
- https://access.redhat.com/errata/RHSA-2019:2690
- https://security.netapp.com/advisory/ntap-20190919-0003/
- https://access.redhat.com/errata/RHBA-2019:2816
- https://access.redhat.com/errata/RHBA-2019:2824
- https://access.redhat.com/errata/RHSA-2019:2769