Описание
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2020-8563
- https://github.com/kubernetes/kubernetes/issues/95621
- https://github.com/kubernetes/kubernetes/pull/95236
- https://github.com/kubernetes/kubernetes/pull/95236/commits/247f6dd09299bc7893c1e0affea11c0255025b96
- https://bugzilla.redhat.com/show_bug.cgi?id=1886635
- https://groups.google.com/g/kubernetes-announce/c/ScdmyORnPDk
- https://groups.google.com/g/kubernetes-security-discuss/c/vm-HcrFUOCs/m/36utxAM5CwAJ
- https://security.netapp.com/advisory/ntap-20210122-0006
Пакеты
github.com/kubernetes/kubernetes
< 1.19.3
1.19.3
Связанные уязвимости
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.
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.
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.
In Kubernetes clusters using VSphere as a cloud provider, with a loggi ...