KubernetesApplication
CVE-2018-1002100
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe kubectl cp command in vulnerable Kubernetes versions does not properly validate tar file paths extracted from containers, allowing a malicious container to include path traversal sequences (e.g., ../../) that cause files to be written to arbitrary locations on the user's local filesystem during the extraction process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KubernetesApplication
>= 1.5.0, <= 1.5.9>= 1.6.0, <= 1.6.14>= 1.7.0, <= 1.7.17>= 1.8.0, <= 1.8.15>= 1.9.0, <= 1.9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed kubectl versionRun 'kubectl version --client' to get the client version. Alternatively, check the binary with 'kubectl version --client --output=yaml' or check the file metadata of the kubectl binary.Affected if The version falls within these ranges: 1.5.0-1.5.9, 1.6.0-1.6.14, 1.7.0-1.7.17, 1.8.0-1.8.15, or 1.9.0-1.9.5.
-
Identify use of kubectl cp commandReview bash history, audit logs, or cluster event logs for any instances of 'kubectl cp' being executed to copy files from containers. Check for commands like 'kubectl cp <pod>:/path/to/file ./local/path'.Affected if kubectl cp has been used to copy files FROM a container to the local filesystem.
-
Assess container trustworthinessIdentify which containers have been sources for kubectl cp operations and evaluate whether they could contain maliciously crafted tar files. Review container images, sources, and deployment configurations.Affected if Containers used as sources for kubectl cp are untrusted, compromised, or from unknown sources.
-
Check for suspicious file creation patternsInspect the local filesystem for any files created via kubectl cp that may have landed in unexpected directories. Review recent file creation timestamps matching kubectl cp usage.Affected if Files appear in directories outside the intended destination, indicating successful path traversal exploitation.
You are affected if your kubectl client version is 1.5.0 through 1.9.5 AND you have used kubectl cp to copy files from containers, especially untrusted ones.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade kubectl and Kubernetes components to version 1.9.6 or later to obtain the patched version. Avoid using kubectl cp with untrusted containers until the upgrade is complete.
Fix this in Kubernetes
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1002100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1002100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data