First published: Fri Oct 09 2020(Updated: )
A flaw was found in kubernetes. Clusters running on VSphere, using VSphere as a cloud provider a with logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log.
Credit: jordan@liggitt.net jordan@liggitt.net
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openshift | <0:4.6.0-202012051246.p0.git.94231.efc9027.el8 | 0:4.6.0-202012051246.p0.git.94231.efc9027.el8 |
Kubernetes Kubernetes | <1.19.3 | |
redhat/kubernetes | <1.19.3 | 1.19.3 |
go/github.com/kubernetes/kubernetes | <1.19.3 | 1.19.3 |
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-8563 is medium with a CVSS score of 6.3.
CVE-2020-8563 affects Kubernetes clusters running on VSphere, using VSphere as a cloud provider with a logging level set to 4 or above.
In CVE-2020-8563, VSphere cloud credentials are leaked in the cloud controller manager's log.
To fix CVE-2020-8563, upgrade to Kubernetes version 1.19.3.
Yes, OpenShift is affected by CVE-2020-8563. To fix it, upgrade to OpenShift version 4.6.0-202012051246.p0.git.94231.efc9027.el7 or later.