CVE-2019-11250 Kubernetes client-go logs authorization headers at debug verbosity levels
Attackers can read sensitive authorization headers from logs if Kubernetes components run at high verbosity levels, exposing credentials.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-11250?
CVE-2019-11250 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 29 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-532
Which versions are affected by CVE-2019-11250?
5 open source packages ship an affected version, including k8s.io/kubernetes and k8s.io/client-go. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
k8s.io/kubernetes Go | All versions | 1.16.0-beta.1 |
k8s.io/kubernetes Go | All versions | 1.16.0-beta.1 |
k8s.io/client-go Go | All versions | 0.17.0 |
k8s.io/client-go Go | All versions | 0.17.0 |
k8s.io/client-go Go | All versions | 0.17.0 |
Linux distribution packages (13)
atomic-openshift Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-clients Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-clients-redistributable Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-docker-excluder Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-excluder Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-hyperkube Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-hypershift Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-master Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-node Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-pod Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-sdn-ovs Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-template-service-broker Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
atomic-openshift-tests Red Hat:openshift:3.11::el7 | All versions | 0:3.11.157-1.git.0.dfe38da.el7 |
Products include Kubernetes Kubernetes, Redhat Openshift Container Platform.
How do I fix CVE-2019-11250?
Upgrade k8s.io/kubernetes to 1.16.0-beta.1 or later.
Is CVE-2019-11250 being exploited?
There is no known exploitation of CVE-2019-11250 in the wild and no public exploit code.
Other vulnerabilities in Kubernetes Kubernetes
- CVE-2018-1002105 Privilege Escalation in Kubernetes
- CVE-2017-1000056 Kubernetes Privilege Escalation
- CVE-2016-1906 Authorization bypass in Openshift
- CVE-2023-3676 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
- CVE-2023-3955 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
Sources
Also known as CLEANSTART-2026-LR86160, DEBIAN-CVE-2019-11250, GHSA-jmrx-5g74-6v2f, GO-2021-0065, RHSA-2019:4052.