The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a t…
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.
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
https://cwe.mitre.org/data/definitions/59.html →Open in CWE collection →An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
https://capec.mitre.org/data/definitions/17.html →Open in CAPEC collection →An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
https://capec.mitre.org/data/definitions/35.html →Open in CAPEC collection →An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
https://capec.mitre.org/data/definitions/76.html →Open in CAPEC collection →An adversary positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name.
https://capec.mitre.org/data/definitions/132.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| ansible-service-broker | Tracked | |
| atomic-enterprise-service-catalog | Tracked | |
| atomic-enterprise-service-catalog | Tracked | |
| atomic-openshift | Tracked | |
| atomic-openshift | Tracked | |
| atomic-openshift | Tracked | |
| atomic-openshift-cluster-autoscaler | Tracked | |
| atomic-openshift-descheduler | Tracked | |
| atomic-openshift-descheduler | Tracked | |
| atomic-openshift-dockerregistry | Tracked | |
| atomic-openshift-dockerregistry | Tracked | |
| atomic-openshift-dockerregistry | Tracked | |
| atomic-openshift-metrics-server | Tracked | |
| atomic-openshift-node-problem-detector | Tracked | |
| atomic-openshift-node-problem-detector | Tracked | |
| atomic-openshift-service-idler | Tracked | |
| atomic-openshift-web-console | Tracked | |
| atomic-openshift-web-console | Tracked | |
| atomic-openshift-web-console | Tracked | |
| cri-o | Tracked |