CVE-2017-1002101: Critical severity kubernetes dashboard vulnerability
In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with any volume type (including non-privileged pods, subject to file permissions) can access files/directories outside of the volume, including the host's filesystem.
Other sources
It was found that volume security can be sidestepped with innocent emptyDir and subpath. A pod could give full control over node host by gaining access to docker socket.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is CVE-2017-1002101?
CVE-2017-1002101 is a vulnerability in Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x, and prior to versions 1.7.14, 1.8.9, and 1.9.4 that allows containers using subpath volume mounts to access files/directories outside of the volume, including the host's filesystem.
What is the severity of CVE-2017-1002101?
The severity of CVE-2017-1002101 is critical with a CVSS score of 9.6.
How can I check if my Kubernetes version is affected by CVE-2017-1002101?
You can check if your Kubernetes version is affected by CVE-2017-1002101 by verifying if it falls within the vulnerable version ranges: 1.3.x, 1.4.x, 1.5.x, 1.6.x, and prior to versions 1.7.14, 1.8.9, and 1.9.4.
How do I fix CVE-2017-1002101 in Kubernetes?
To fix CVE-2017-1002101 in Kubernetes, you need to upgrade to versions 1.7.14, 1.8.9, or 1.9.4 or later.
Where can I find more information about CVE-2017-1002101?
You can find more information about CVE-2017-1002101 in the following references: [https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1554420](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1554420), [https://access.redhat.com/errata/RHSA-2018:0475](https://access.redhat.com/errata/RHSA-2018:0475), [https://github.com/kubernetes/kubernetes/issues/60813](https://github.com/kubernetes/kubernetes/issues/60813).