LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1002201: zt-zip before 1.13 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via...

zt-zip before 1.13 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-1002201 affects the zt-zip Java library before version 1.13. If an application extracts a malicious ZIP archive with this library, crafted archive entries can escape the intended folder and overwrite files elsewhere. Business risk depends on whether the application processes untrusted ZIP files.

Executive priority

Prioritize remediation for internet-facing or partner-facing systems that accept ZIP uploads or archive imports. For internal-only use with trusted archives, treat as important dependency cleanup, but still patch because arbitrary file write can become severe in sensitive deployments.

Technical view

The flaw is a CWE-22 directory traversal issue in zt-zip extraction handling, also described as Zip Slip. ZIP entry paths containing parent-directory traversal can be mishandled during extraction, allowing arbitrary file writes outside the target directory. The bundle identifies zt-zip before 1.13 as vulnerable.

Likely exposure

Exposure is most likely in Java applications using org.zeroturnaround zt-zip before 1.13 to extract ZIP files, especially upload, import, plugin, backup, or integration workflows that accept archives from users or external systems.

Exploitation context

The provided sources describe arbitrary file write through malicious ZIP entries. The bundle does not show CISA KEV listing or cited evidence of active exploitation for this CVE, so active exploitation should not be assumed from this evidence alone.

Researcher notes

Focus on dependency presence and reachable extraction paths, not just package inventory. Evidence supports zt-zip before 1.13, CWE-22, and Zip Slip-style arbitrary file write. The bundle does not provide CVSS, KEV status, or confirmed exploitation details.

Mitigation direction

  • Upgrade zt-zip to version 1.13 or later.
  • Check vendor and Snyk guidance for current supported versions.
  • Avoid extracting untrusted ZIP archives with vulnerable zt-zip versions.
  • Restrict archive extraction paths and file permissions where feasible.

Validation and detection

  • Inventory dependency manifests, lockfiles, SBOMs, and runtime artifacts for zt-zip versions below 1.13.
  • Identify application paths that extract ZIP files from users or external systems.
  • Confirm patched zt-zip is present in built and deployed artifacts.
  • Review logs and file integrity signals for unexpected writes near archive-processing workflows.
Prepared
Confidence
high
Sources
7

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.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell 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-1002201 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zeroturnaroundzt-zipunspecifiedListed
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.