Path traversal via non-tar copyDirectoryFromPod
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | kubernetes-client/java | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | Java |
|
Vendor Workaround
Prior to upgrading, this vulnerability can be mitigated by ensuring you only copy files from trusted pods, or by ensuring tar is available in the container to use the secure tar-based copy path.
No CVSS v4.0
No CVSS v3.1
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.377% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/kubernetes-client/java/issues/4861 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kubernetes
Kubernetes java |
|
| Vendors & Products |
Kubernetes
Kubernetes java |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A security issue was discovered in the Kubernetes Java client library where a compromised pod may be able to create new files in arbitrary locations on the client machine executing copy operations via non-tar copyDirectoryFromPod when enableTarCompressing is false. | |
| Title | Path traversal via non-tar copyDirectoryFromPod | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_0
|