Ceph RBD adminSecrets exposed in logs when loglevel >= 4
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kubernetes Go |
|
|
| k8s.io/kubernetes Go |
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kubernetes Go |
|
|
| k8s.io/kubernetes Go |
< 1.17.13≥ 1.18.0 · < 1.18.10≥ 1.19.0 · < 1.19.3
|
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-manager's logs during provisioning of Ceph RBD persistent claims. This affects < v1.19.3, < v1.18.10, < v1.17.13.
From the CVE record · kubernetes
In clusters using Ceph RBD as a storage provisioner with logging level 4 or higher, kube-controller-manager can write Ceph RBD admin secrets to its logs while provisioning persistent claims. Someone with access to those logs could read the secrets; the input does not specify whether network access, authentication, or user interaction is required.
Operators of Kubernetes clusters using Ceph RBD should check installations before 1.17.13, from 1.18.0 to before 1.18.10, or from 1.19.0 to before 1.19.3, including the corresponding Go packages github.com/kubernetes/kubernetes and k8s.io/kubernetes.