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.
access.redhat.com/errata/RHSA-2018:3537
access.redhat.com/errata/RHSA-2018:3549
access.redhat.com/errata/RHSA-2018:3551
access.redhat.com/errata/RHSA-2018:3598
access.redhat.com/errata/RHSA-2018:3624
access.redhat.com/errata/RHSA-2018:3742
access.redhat.com/errata/RHSA-2018:3752
access.redhat.com/errata/RHSA-2018:3754
github.com/evict/poc_CVE-2018-1002105
github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905
github.com/kubernetes/kubernetes/issues/71411
groups.google.com/forum/#!topic/kubernetes-announce/GVllWCg6L88
lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html
nvd.nist.gov/vuln/detail/CVE-2018-1002105
security.netapp.com/advisory/ntap-20190416-0001
www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do
www.exploit-db.com/exploits/46052
www.exploit-db.com/exploits/46053
www.openwall.com/lists/oss-security/2019/06/28/2
www.openwall.com/lists/oss-security/2019/07/06/3
www.openwall.com/lists/oss-security/2019/07/06/4
www.securityfocus.com/bid/106068