Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel >= 9
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/client-go Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/client-go Go |
|
|
0.17.16| k8s.io/kubernetes Go |
|
|
In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.
From the CVE record · kubernetes
When the logging level is set to at least 9, Kubernetes can write authorization and bearer tokens to API server logs or client tool output such as kubectl. Anyone who can read that output may see the tokens; the input does not specify a network attack, authentication requirement, or user interaction.
Operators running Kubernetes versions <=1.19.3, <=1.18.10, <=1.17.13, or <1.20.0-alpha2, and users of the listed affected k8s.io/client-go or k8s.io/kubernetes packages, should check their deployments.