CVE-2019-11251GO-2022-0802GHSA-6QFG-8799-R575
kubectl cp allows symlink directory traversal
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.13.11, 1.14.7, 1.16.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes Kubernetes
prior to 1.13.11, prior to 1.14.7, prior to 1.15.4, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12
- k8s.io/kubernetesGo
From 1.13.10 · fixed in 1.13.11; From 1.14.6 · fixed in 1.14.7; From 1.15.3 · fixed in 1.16.0
- k8s.io/kubernetesGo
From 1.13.10 · fixed in 1.13.11
- k8s.io/kubernetesGo
From 1.14.6 · fixed in 1.14.7
- k8s.io/kubernetesGo
From 1.15.3 · fixed in 1.16.0