CVE-2019-1002101

MEDIUMNVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.4 under NVD CVSS v3. EPSS exploit probability: 13.2%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 13%CVSS: 6.4Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.4
EG Score
6.4(medium)
EPSS
96.0%
KEV
Not listed

Published

April 1, 2019

Last Modified

November 21, 2024

References (21)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-fluent-plugin-viaq_data_model-0:0.0.18-1.el72019-04-11redhat
redhatopenshift-ansible-0:3.9.74-1.git.0.70a0a63.el72019-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
k8s.io/kubernetes—1.13.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:18 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-20 19:02 UTCOSV refresh
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-13 22:27 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-09 19:06 UTCEPSS rescore
  15. 2026-07-08 15:11 UTCEPSS rescore
  16. 2026-07-08 15:11 UTCEPSS rescore
  17. 2026-07-07 13:42 UTCEPSS rescore
  18. 2026-07-07 13:42 UTCEPSS rescore
  19. 2026-07-06 16:25 UTCEPSS rescore
  20. 2026-07-06 16:24 UTCEPSS rescore
  21. 2026-07-06 02:20 UTCEPSS rescore
  22. 2026-07-05 02:27 UTCEPSS rescore
  23. 2026-07-04 06:28 UTCEPSS rescore
  24. 2026-07-04 06:28 UTCEPSS rescore
  25. 2026-07-03 14:26 UTCOSV refresh
Show 60 more
  1. 2026-07-01 15:03 UTCEPSS rescore
  2. 2026-07-01 15:03 UTCEPSS rescore
  3. 2026-06-30 23:20 UTCEPSS rescore
  4. 2026-06-30 23:20 UTCEPSS rescore
  5. 2026-06-29 14:03 UTCEPSS rescore
  6. 2026-06-28 14:04 UTCEPSS rescore
  7. 2026-06-28 04:53 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-27 03:06 UTCEPSS rescore
  10. 2026-06-27 03:06 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-21 14:54 UTCEPSS rescore
  18. 2026-06-21 14:54 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-19 19:23 UTCEPSS rescore
  22. 2026-06-19 19:23 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
  26. 2026-06-16 17:50 UTCEPSS rescore
  27. 2026-06-16 17:50 UTCEPSS rescore
  28. 2026-06-15 17:45 UTCEPSS rescore
  29. 2026-06-15 04:13 UTCOSV refresh
  30. 2026-06-13 22:58 UTCEPSS rescore
  31. 2026-06-12 23:09 UTCEPSS rescore
  32. 2026-06-12 23:09 UTCEPSS rescore
  33. 2026-06-11 13:57 UTCEPSS rescore
  34. 2026-06-10 22:16 UTCEPSS rescore
  35. 2026-06-10 13:19 UTCEPSS rescore
  36. 2026-06-07 15:22 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-06 13:45 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-05 22:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-05-31 22:29 UTCEPSS rescore
  49. 2026-05-31 22:29 UTCEPSS rescore
  50. 2026-05-31 00:14 UTCEPSS rescore
  51. 2026-05-31 00:14 UTCEPSS rescore
  52. 2026-05-29 13:41 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-27 21:14 UTCEG score recompute
  56. 2026-05-27 21:14 UTCVendor advisory
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore
  60. 2026-05-25 08:16 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCbrompwnie/CVE-2019-1002101-Helpers
    First seen Apr 3, 2019

    PoC helper scripts and Dockerfile for CVE-2019-1002101

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-1002101?
CVE-2019-1002101 is a medium vulnerability published on April 1, 2019. 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…
When was CVE-2019-1002101 disclosed?
CVE-2019-1002101 was first published in the National Vulnerability Database on April 1, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1002101 actively exploited?
CVE-2019-1002101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-1002101?
CVE-2019-1002101 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2019-1002101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1002101, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-1002101

Explore →

Is Your Infrastructure Affected by CVE-2019-1002101?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs