# 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. - **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **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:** Yes - **Published:** 29 Aug 2019 - **Updated:** 17 Sep 2024 - **Also known as:** CLEANSTART-2026-LR86160, DEBIAN-CVE-2019-11250, GHSA-jmrx-5g74-6v2f, GO-2021-0065, RHSA-2019:4052 ## 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 (Insertion of Sensitive Information into Log File) ## 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 | Ecosystem | 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 | | `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: 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](https://insights.sbomify.com/CVE-2018-1002105/): Privilege Escalation in Kubernetes (critical 9.8) - [CVE-2017-1000056](https://insights.sbomify.com/CVE-2017-1000056/): Kubernetes Privilege Escalation (critical 9.8) - [CVE-2016-1906](https://insights.sbomify.com/CVE-2016-1906/): Authorization bypass in Openshift (critical 9.8) - [CVE-2023-3676](https://insights.sbomify.com/CVE-2023-3676/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8) - [CVE-2023-3955](https://insights.sbomify.com/CVE-2023-3955/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-11250 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2019-11250 in the wild and no public exploit code. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.16.0-beta.1 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.16.0-beta.1 - k8s.io/client-go (Go): affected all versions; fixed in 0.17.0 - k8s.io/client-go (Go): affected all versions; fixed in 0.17.0 - k8s.io/client-go (Go): affected all versions; fixed in 0.17.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-11250/ (Markdown: https://insights.sbomify.com/CVE-2019-11250/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11250 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11250 - OSV: https://osv.dev/vulnerability/CVE-2019-11250 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-11250/ Summaries are generated and may contain mistakes; the official description above is the record.