CVE-2018-1002105

Public Exploit

Description

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 90.41% Top 5%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory opensuse.org
Affected: Kubernetes Kubernetes
Published at:
Updated at:

References

Link Tags
https://groups.google.com/forum/#%21topic/kubernetes-announce/GVllWCg6L88
https://www.exploit-db.com/exploits/46053/ exploit vdb entry third party advisory
https://access.redhat.com/errata/RHSA-2018:3549 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:3752 third party advisory vendor advisory
https://www.exploit-db.com/exploits/46052/ exploit vdb entry third party advisory
https://access.redhat.com/errata/RHSA-2018:3624 third party advisory vendor advisory
https://www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do third party advisory mitigation
https://github.com/kubernetes/kubernetes/issues/71411 issue tracking patch mitigation third party advisory
https://access.redhat.com/errata/RHSA-2018:3742 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:3754 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:3537 third party advisory vendor advisory
https://github.com/evict/poc_CVE-2018-1002105 third party advisory exploit
https://access.redhat.com/errata/RHSA-2018:3598 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:3551 third party advisory vendor advisory
http://www.securityfocus.com/bid/106068 vdb entry third party advisory
https://security.netapp.com/advisory/ntap-20190416-0001/ third party advisory
http://www.openwall.com/lists/oss-security/2019/06/28/2 mailing list
http://www.openwall.com/lists/oss-security/2019/07/06/3 mailing list
http://www.openwall.com/lists/oss-security/2019/07/06/4 mailing list
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html vendor advisory

Frequently Asked Questions

What is the severity of CVE-2018-1002105?
CVE-2018-1002105 has been scored as a critical severity vulnerability.
How to fix CVE-2018-1002105?
To fix CVE-2018-1002105, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-1002105 being actively exploited in the wild?
It is possible that CVE-2018-1002105 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~90% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-1002105?
CVE-2018-1002105 affects Kubernetes Kubernetes.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.