CVE-2019-1002101 kubectl cp path traversal

Medium 6.4 Published 1 Apr 2019 Updated 16 Sep 2024

A malicious tar binary in a container can exploit kubectl cp to write files to arbitrary paths on the user's machine, potentially executing code.

Exploited in the wild: Not known
Login needed: An administrator
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: Available

What is CVE-2019-1002101?

CVE-2019-1002101 is a medium-severity path traversal vulnerability in Kubernetes Kubernetes, published on 1 Apr 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

Official description

The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a tar inside the container, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. The untar function can both create and follow symbolic links. The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0.

Weakness: CWE-59

Which versions are affected by CVE-2019-1002101?

7 open source packages ship an affected version, including k8s.io/kubernetes. It affects 2 products.

Package	Affected	Fixed in
`k8s.io/kubernetes` Go	All versions	`1.11.9, 1.12.7, 1.13.5`
`k8s.io/kubernetes` Go	All versions	`1.11.9`
`k8s.io/kubernetes` Go	All versions	`1.11.9`
`k8s.io/kubernetes` Go	From `1.12.0`	`1.12.7`
`k8s.io/kubernetes` Go	From `1.12.0`	`1.12.7`
`k8s.io/kubernetes` Go	From `1.13.0`	`1.13.5`

1 more packages

k8s.io/kubernetes Go From 1.13.0 1.13.5

Linux distribution packages (33)

`atomic-enterprise-service-catalog` Red Hat:openshift:3.10::el7	All versions	`1:3.10.127-1.git.55.b54f8c7.el7`
`atomic-enterprise-service-catalog-svcat` Red Hat:openshift:3.10::el7	All versions	`1:3.10.127-1.git.55.b54f8c7.el7`
`atomic-openshift` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-clients` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-clients-redistributable` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-descheduler` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.153.bc1eddd.el7`
`atomic-openshift-docker-excluder` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-dockerregistry` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.f8aa6dd.el7`
`atomic-openshift-excluder` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-hyperkube` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-hypershift` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-master` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-node` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-node-problem-detector` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.4f5519b.el7`
`atomic-openshift-pod` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-sdn-ovs` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-template-service-broker` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-tests` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.dab74c6.el7`
`atomic-openshift-web-console` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.50.eab7949.el7`
`golang-github-prometheus-node_exporter` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.8ebe819.el7`
`openshift-ansible` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.131da09.el7`
`openshift-ansible-docs` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.131da09.el7`
`openshift-ansible-playbooks` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.131da09.el7`
`openshift-ansible-roles` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.131da09.el7`
`openshift-enterprise-cluster-capacity` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.44580c6.el7`
`prometheus-node-exporter` Red Hat:openshift:3.10::el7	All versions	`0:3.10.127-1.git.0.8ebe819.el7`
`python-libcloud` Red Hat:openshift:3.10::el7	All versions	`0:2.2.1-20180102gitd701bf9.el7`
`rubygem-fluent-plugin-viaq_data_model` Red Hat:openshift:3.10::el7	All versions	`0:0.0.18-1.el7`
`rubygem-fluent-plugin-viaq_data_model-doc` Red Hat:openshift:3.10::el7	All versions	`0:0.0.18-1.el7`
`atomic-enterprise-service-catalog` Red Hat:openshift:3.11::el7	All versions	`1:3.11.98-1.git.0.a7877b0.el7`
`atomic-enterprise-service-catalog-svcat` Red Hat:openshift:3.11::el7	All versions	`1:3.11.98-1.git.0.a7877b0.el7`
`atomic-openshift` Red Hat:openshift:3.11::el7	All versions	`0:3.11.98-1.git.0.0cbaff3.el7`
`atomic-openshift-clients` Red Hat:openshift:3.11::el7	All versions	`0:3.11.98-1.git.0.0cbaff3.el7`

Products include Kubernetes Kubernetes, Redhat Openshift Container Platform.

How do I fix CVE-2019-1002101?

Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.11.9, 1.12.7 or 1.13.5.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2019-1002101 being exploited?

There is no known exploitation of CVE-2019-1002101 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

All Kubernetes Kubernetes vulnerabilities

Sources

Also known as GHSA-34jx-wx69-9x8v, GO-2022-0782, RHBA-2019:0619, RHBA-2019:0620, RHBA-2019:0636.