In Kubernetes clusters using Ceph RBD as a storage provisioner, with logging level of at least 4, Ceph RBD admin secrets can be written to logs. This occurs in kube-controller-managers logs during provisioning of Ceph RBD persistent claims. This affects < v1.19.3, < v1.18.10, < v1.17.13.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kubernetes | Kubernetes | 1.17.0 (including) | 1.17.13 (excluding) |
| Kubernetes | Kubernetes | 1.18.0 (including) | 1.18.10 (excluding) |
| Kubernetes | Kubernetes | 1.19.0 (including) | 1.19.3 (excluding) |
| Red Hat OpenShift Container Platform 4.6 | RedHat | openshift4/ose-hyperkube:v4.6.0-202101090040.p0 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | openshift-0:4.7.0-202102060108.p0.git.97095.7271b90.el8 | * |
| Kubernetes | Ubuntu | groovy | * |
| Kubernetes | Ubuntu | hirsute | * |
| Kubernetes | Ubuntu | impish | * |
| Kubernetes | Ubuntu | kinetic | * |
| Kubernetes | Ubuntu | lunar | * |
| Kubernetes | Ubuntu | mantic | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: