# CVE-2019-11244: kubectl creates world-writeable cached schema files > kubectl writes cached schema files with world-writeable permissions, allowing local attackers to modify them and disrupt kubectl operations. - **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Apr 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-2575-pghm-6qqx, RHSA-2019:3942, RHSA-2020:0020 ## What is CVE-2019-11244? CVE-2019-11244 is a low-severity vulnerability in Kubernetes Kubernetes, published on 22 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-524 (Use of Cache Containing Sensitive Information) ## Which versions are affected by CVE-2019-11244? 2 open source packages ship an affected version, including k8s.io/client-go. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/client-go` | Go | From 1.8.0 | 1.12.9 | | `k8s.io/client-go` | Go | From 1.8.0 | 1.12.9 | | `atomic-openshift` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-clients` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-clients-redistributable` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-docker-excluder` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-excluder` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-hyperkube` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-hypershift` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-master` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-node` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-pod` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-sdn-ovs` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-template-service-broker` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `atomic-openshift-tests` | Red Hat:openshift:3.11::el7 | All versions | 0:3.11.161-1.git.0.4ccbe25.el7 | | `openshift` | Red Hat:openshift:4.1::el7 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el7 | | `openshift-clients` | Red Hat:openshift:4.1::el7 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el7 | | `openshift-clients-redistributable` | Red Hat:openshift:4.1::el7 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el7 | | `openshift-hyperkube` | Red Hat:openshift:4.1::el7 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el7 | | `openshift` | Red Hat:openshift:4.1::el8 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el8 | | `openshift-clients` | Red Hat:openshift:4.1::el8 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el8 | | `openshift-clients-redistributable` | Red Hat:openshift:4.1::el8 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el8 | | `openshift-hyperkube` | Red Hat:openshift:4.1::el8 | All versions | 0:4.1.24-201911080309.git.0.c41acf2.el8 | Products: Kubernetes Kubernetes, Netapp Trident, Redhat Openshift Container Platform. ## How do I fix CVE-2019-11244? Upgrade k8s.io/client-go to 1.12.9 or later. ## Is CVE-2019-11244 being exploited? There is no known exploitation of CVE-2019-11244 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-11244 and fix it if it is affected. What it is: CVE-2019-11244 is a low-severity vulnerability in Kubernetes Kubernetes, published on 22 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-11244 in the wild and no public exploit code. Affected packages and fixed versions: - k8s.io/client-go (Go): affected from 1.8.0; fixed in 1.12.9 - k8s.io/client-go (Go): affected from 1.8.0; fixed in 1.12.9 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-11244/ (Markdown: https://insights.sbomify.com/CVE-2019-11244/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11244 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11244 - OSV: https://osv.dev/vulnerability/CVE-2019-11244 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-11244/ Summaries are generated and may contain mistakes; the official description above is the record.