Описание
Privilege Escalation in Kubernetes
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2018-1002105
- https://github.com/kubernetes/kubernetes/issues/71411
- https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905
- https://www.securityfocus.com/bid/106068
- https://www.openwall.com/lists/oss-security/2019/07/06/4
- https://www.openwall.com/lists/oss-security/2019/07/06/3
- https://www.openwall.com/lists/oss-security/2019/06/28/2
- https://www.exploit-db.com/exploits/46053
- https://www.exploit-db.com/exploits/46052
- https://www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do
- https://security.netapp.com/advisory/ntap-20190416-0001
- https://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html
- https://groups.google.com/forum/#!topic/kubernetes-announce/GVllWCg6L88
- https://github.com/evict/poc_CVE-2018-1002105
- https://access.redhat.com/errata/RHSA-2018:3754
- https://access.redhat.com/errata/RHSA-2018:3752
- https://access.redhat.com/errata/RHSA-2018:3742
- https://access.redhat.com/errata/RHSA-2018:3624
- https://access.redhat.com/errata/RHSA-2018:3598
- https://access.redhat.com/errata/RHSA-2018:3551
- https://access.redhat.com/errata/RHSA-2018:3549
- https://access.redhat.com/errata/RHSA-2018:3537
Пакеты
github.com/kubernetes/kubernetes
< 1.10.11
1.10.11
github.com/kubernetes/kubernetes
>= 1.11.0, < 1.11.5
1.11.5
github.com/kubernetes/kubernetes
>= 1.12.0, < 1.12.3
1.12.3
Связанные уязвимости
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, in ...
