CVE-2019-1002101 Vulnerability Analysis & Exploit Details

CVE-2019-1002101
Vulnerability Scoring

6.4
/10
High Risk

If left unpatched, CVE-2019-1002101 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2019-1002101 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:17 UTC
Originally published on: 🕑 01 Apr 2019, 14:29 UTC

Time between publication and last update: 2060 days

CVSS Release: version 3

CVSS3 Source

josh@bress.net

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H

CVE-2019-1002101 Vulnerability Summary

CVE-2019-1002101: 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.

Assessing the Risk of CVE-2019-1002101

Access Complexity Graph

The exploitability of CVE-2019-1002101 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-1002101

The exploitability of CVE-2019-1002101 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-1002101, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-1002101, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2019-1002101 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2019-1002101 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2019-1002101 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.147% (probability of exploit)

EPSS Percentile: 52.12% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 47.88% of others.

CVE-2019-1002101 References

External References

CWE Common Weakness Enumeration

CWE-59

CAPEC Common Attack Pattern Enumeration and Classification

  • Symlink Attack CAPEC-132 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.
  • Using Malicious Files CAPEC-17 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.
  • Leverage Executable Code in Non-Executable Files CAPEC-35 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.
  • Manipulating Web Input to File System Calls CAPEC-76 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.

Vulnerable Configurations

  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.0:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.1:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.1:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.1:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.1:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.2:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.2:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.2:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.2:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.3:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.3:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.3:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.3:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.4:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.4:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.4:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.4:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.5:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.5:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.5:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.5:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.6:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.6:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.6:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.6:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.7:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.7:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.7:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.7:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.8:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.8:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.11.8:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.11.8:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:alpha0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:alpha0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.1:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.1:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.1:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.1:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.2:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.2:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.2:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.2:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.3:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.3:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.3:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.3:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.4:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.4:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.4:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.4:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.5:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.5:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.5:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.5:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.6:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.6:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.12.6:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.12.6:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha2:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha3:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.0:alpha3:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.1:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.1:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.1:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.1:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.2:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.2:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.2:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.2:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.3:-:*:*:*:-:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.3:-:*:*:*:-:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.3:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.3:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.4:-:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.4:-:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.4:*:*:*:*:-:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.4:*:*:*:*:-:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.13.4:beta0:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.13.4:beta0:*:*:*:*:*:*
  • cpe:2.3:a:kubernetes:kubernetes:1.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:kubernetes:kubernetes:1.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openshift_container_platform:3.9:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openshift_container_platform:3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openshift_container_platform:3.10:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openshift_container_platform:3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-1002101: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3797 – A vulnerability classified as critical was found in SeaCMS up to 13.3. This vulnerability affects unknown code of the file /admin_topic.php?action=...
  • CVE-2025-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...