Kubernetes client-go logs authorization headers at debug verbosity levels
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/client-go Go |
|
|
| k8s.io/kubernetes Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/client-go Go |
|
|
| k8s.io/kubernetes Go |
|
|
The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected.
From the CVE record · kubernetes
The Kubernetes client-go library logs request headers at verbosity level 7 or higher. When components using basic or bearer token authentication run at that verbosity, credentials can be disclosed to unauthorized users through logs or command output.
Check deployments using Go k8s.io/client-go before 0.17.0 or k8s.io/kubernetes before 1.16.0-beta.1, particularly components running at high verbosity.