CVE-2020-8563
published 2020-12-07CVE-2020-8563: In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud…
PriorityP423medium5.5CVSS 3.1
AVLACLPRLUINSUCHINAN
EPSS
0.51%
39.3th percentile
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | kubernetes | — | — |
| github.com | kubernetes_kubernetes | >= 0 < 1.19.3 | 1.19.3 |
| k8s.io | kubernetes | >= 0 < 1.19.3 | 1.19.3 |
| kubernetes | kubernetes | < 1.19.3 | 1.19.3 |
| msrc | cm1_kubernetes-1.18.14_1.18.14-8_on_cbl_mariner_1.0 | — | — |
| msrc | cm1_kubernetes-1.18.17_1.18.17-6_on_cbl_mariner_1.0 | — | — |
| msrc | cm1_kubernetes-1.18.17_1.18.17-9_on_cbl_mariner_1.0 | — | — |
| msrc | cm1_kubernetes-1.18.19_1.18.19-2_on_cbl_mariner_1.0 | — | — |
| msrc | cm1_kubernetes_1.18.17-5_on_cbl_mariner_1.0 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:P/I:N/A:N
osv5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_debian4.7LOW
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Microsoft
Secret leaks in logs for vSphere Provider kube-controller-manager
vendor_msrc·2020-12-08·CVSS 5.5
CVE-2020-8563 [MEDIUM] CWE-532 Secret leaks in logs for vSphere Provider kube-controller-manager
Secret leaks in logs for vSphere Provider kube-controller-manager
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
kubernetes: kubernetes
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Refe
Red Hat
kubernetes: Secret leaks in kube-controller-manager when using vSphere Provider
vendor_redhat·2020-10-14·CVSS 4.7
CVE-2020-8563 [MEDIUM] CWE-117 kubernetes: Secret leaks in kube-controller-manager when using vSphere Provider
kubernetes: Secret leaks in kube-controller-manager when using vSphere Provider
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
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.
Statement: OpenShift Container Platform (OCP) versions before 4.6 are not affected by this vulnerability as they are based on Kubernetes versions before 1.19. Only Kubernetes versions 1.19.0 through 1.19.2 are affected by this vulnerability.
Mitigation: Ensure that the logging level is below 4. Add
Debian
CVE-2020-8563: kubernetes - In Kubernetes clusters using VSphere as a cloud provider, with a logging level s...
vendor_debian·2020·CVSS 4.7
CVE-2020-8563 [MEDIUM] CVE-2020-8563: kubernetes - In Kubernetes clusters using VSphere as a cloud provider, with a logging level s...
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
OSV
Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes
osv·2024-06-05
CVE-2020-8563 Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes
Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes
Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes
GHSA
Sensitive Information leak via Log File in Kubernetes
ghsa·2024-04-24
CVE-2020-8563 [MEDIUM] CWE-532 Sensitive Information leak via Log File in Kubernetes
Sensitive Information leak via Log File in Kubernetes
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
OSV
Sensitive Information leak via Log File in Kubernetes
osv·2024-04-24
CVE-2020-8563 [MEDIUM] Sensitive Information leak via Log File in Kubernetes
Sensitive Information leak via Log File in Kubernetes
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
OSV
CVE-2020-8563: In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the clou
osv·2020-12-07·CVSS 5.5
CVE-2020-8563 [MEDIUM] CVE-2020-8563: In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the clou
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
No detection rules found.
No public exploits indexed.
https://github.com/kubernetes/kubernetes/issues/95621https://groups.google.com/g/kubernetes-security-discuss/c/vm-HcrFUOCs/m/36utxAM5CwAJhttps://security.netapp.com/advisory/ntap-20210122-0006/https://github.com/kubernetes/kubernetes/issues/95621https://groups.google.com/g/kubernetes-security-discuss/c/vm-HcrFUOCs/m/36utxAM5CwAJhttps://security.netapp.com/advisory/ntap-20210122-0006/
2020-12-07
Published