LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1002100: In Kubernetes versions 1.5.x, 1.6.x, 1.7.x, 1.8.x, and prior to version 1.9.6, the kubectl cp command insec...

In Kubernetes versions 1.5.x, 1.6.x, 1.7.x, 1.8.x, and prior to version 1.9.6, the kubectl cp command insecurely handles tar data returned from the container, and can be caused to overwrite arbitrary local files.

MediumCVSS 4.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects older Kubernetes kubectl cp behavior. If an operator copies files from a malicious or compromised container, crafted tar data can overwrite arbitrary files on the operator’s local machine. The main business risk is integrity damage to administrator or CI workstations, not direct cluster takeover by itself.

Executive priority

Treat this as a moderate operational hygiene issue. It is not described as remotely exploitable without user action, but old admin tooling can let a compromised workload tamper with privileged operator or CI machines.

Technical view

Kubernetes 1.5.x, 1.6.x, 1.7.x, 1.8.x, and versions before 1.9.6 are reported affected. kubectl cp insecurely handles tar data returned by a container, allowing arbitrary local file overwrite when a user runs the copy operation. CVSS 3.0 is 4.2 with high privileges and user interaction required.

Likely exposure

Exposure is most likely where old kubectl clients remain on administrator laptops, jump hosts, or CI systems and are used to copy files from pods or containers. The issue depends on interacting with a hostile or compromised container.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires a user to run kubectl cp and accept tar data from the container. Impact is local file overwrite on the machine running kubectl.

Researcher notes

The vulnerability is in kubectl cp tar stream handling, not a generic Kubernetes API compromise. Evidence in the bundle identifies affected version ranges and overwrite impact, but does not provide a detailed exploit timeline, active exploitation evidence, or complete distribution-specific fix matrix.

Mitigation direction

  • Upgrade kubectl/Kubernetes client tooling to 1.9.6 or a later vendor-fixed supported release.
  • Check vendor advisories for backported fixes in Kubernetes distributions such as Red Hat or OpenShift.
  • Avoid using kubectl cp from sensitive workstations against untrusted or compromised containers.
  • Retire unsupported Kubernetes 1.5.x through 1.8.x client tooling from admin and CI environments.

Validation and detection

  • Inventory kubectl versions on administrator laptops, jump hosts, and CI runners.
  • Search automation and runbooks for kubectl cp usage against containers.
  • Confirm Kubernetes client packages are 1.9.6 or vendor-fixed builds.
  • Review RBAC and operational access for users who copy files from pods.
  • Check incident history for suspicious local file changes after kubectl cp activity.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1002100 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.2 (3.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.2CVSS 3.0MediumCVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N0.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.2Medium
CVSS 3.0 vector shape for CVE-2018-1002100Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KubernetesKubernetesv1.5.x, v1.6.x, v1.7.x, v1.8.x, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.