Docker config secrets leaked when file is malformed and 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.20.0-alpha.1
|
In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13.
From the CVE record · kubernetes
In Kubernetes clusters with logging level 4 or higher, processing a malformed docker config file can leak its contents into logs, including pull secrets or registry credentials. Someone with access to those logs could read the exposed credentials; the input does not specify authentication or user-interaction requirements.
Operators of affected Kubernetes clusters and users of Go packages github.com/kubernetes/kubernetes or k8s.io/kubernetes should check their versions against the listed affected ranges.