CVE-2017-1000056: Critical severity kubernetes dashboard vulnerability
Published Jul 13, 2017
·Updated
Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to make use of any existing PodSecurityPolicy object.
Affected Software
6 affected componentsFixes available
go/k8s.io/kubernetes>=1.5.0<1.5.5
1.5.5
Kubernetes kubernetes=1.5.0
Kubernetes kubernetes=1.5.1
Kubernetes kubernetes=1.5.2
Kubernetes kubernetes=1.5.3
Kubernetes kubernetes=1.5.4
Event History
Jul 13, 2017
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
May 12, 2021
Advisory Published
06:16 PM
Frequently Asked Questions
1
What is the severity of CVE-2017-1000056?
CVE-2017-1000056 is classified as a high severity vulnerability.
2
How do I fix CVE-2017-1000056?
To fix CVE-2017-1000056, you should upgrade Kubernetes to version 1.5.5 or later.
3
Which versions of Kubernetes are affected by CVE-2017-1000056?
Kubernetes versions 1.5.0 to 1.5.4 are vulnerable to CVE-2017-1000056.
4
What type of vulnerability is CVE-2017-1000056?
CVE-2017-1000056 is a privilege escalation vulnerability in the PodSecurityPolicy admission plugin.
5
Can I still use Kubernetes 1.5.0 if I apply security measures against CVE-2017-1000056?
No, it is not recommended to use Kubernetes 1.5.0 as it remains vulnerable to CVE-2017-1000056 regardless of additional security measures.