Skip to content
Fencer Intel
low 3.3

CVE-2019-11244 json

kubectl creates world-writeable cached schema files

published 7y ago modified 4mo ago also GHSA-2575-pghm-6qqx , EUVD-2022-0756

cvss
3.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • go k8s.io/client-go 1.12.9
  • atomic-openshift openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-pod openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-node openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-tests openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-master openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-clients openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-sdn-ovs openshift 3.11 3.11.161-1.git.0.4ccbe25.el7
  • atomic-openshift-excluder openshift 3.11 3.11.161-1.git.0.4ccbe25.el7

red hat advisories RHSA-2020:0020RHSA-2019:3942

Is CVE-2019-11244 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-11244 updated cvss 3.3

kubernetes: Schema info written with world-writeable permissions when cached

  • Red Hat OpenShift Container Platform 3.9 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +8 more Red Hat OpenShift Container Platform 3.10 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more
    affected: workaround, no fix available “Do not use --cache-dir, or ensure that --cache-dir is not set to a location that other users have access to.”
  • Red Hat OpenShift Container Platform 3.11 atomic-openshift 3.11.161-1.git.0.4ccbe25.el7, atomic-openshift-pod 3.11.161-1.git.0.4ccbe25.el7, atomic-openshift-node 3.11.161-1.git.0.4ccbe25.el7, atomic-openshift-tests 3.11.161-1.git.0.4ccbe25.el7, atomic-openshift-master 3.11.161-1.git.0.4ccbe25.el7, atomic-openshift-clients 3.11.161-1.git.0.4ccbe25.el7, +7 more
    fixed: vendor fix “Do not use --cache-dir, or ensure that --cache-dir is not set to a location that other users have access to.” RHSA-2020:0020
  • Red Hat OpenShift Container Platform 4.1 openshift4/ose-cli v4.1.24-201911120311, openshift 4.1.24-201911080309.git.0.c41acf2.el7, openshift 4.1.24-201911080309.git.0.c41acf2.el8, openshift-clients 4.1.24-201911080309.git.0.c41acf2.el7, openshift-clients 4.1.24-201911080309.git.0.c41acf2.el8, openshift-hyperkube 4.1.24-201911080309.git.0.c41acf2.el7, +3 more
    fixed: vendor fix “Do not use --cache-dir, or ensure that --cache-dir is not set to a location that other users have access to.” RHSA-2019:3942
  • Red Hat OpenShift Container Platform 3.6 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +9 more Red Hat OpenShift Container Platform 3.7 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +10 more Red Hat Storage 3 heketi, heketi-client, python-heketi
    not affected: vulnerable code not present “Do not use --cache-dir, or ensure that --cache-dir is not set to a location that other users have access to.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 3.3 CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
NVD 3.1 5.0 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 5.0 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go k8s.io/client-go
>=1.8.0, <1.12.9
1.12.9

Affected products

  • Kubernetes Kubernetes

Classification

Weakness
  • CWE-524 Use of Cache Containing Sensitive Information
  • CWE-732 Incorrect Permission Assignment for Critical Resource
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.