CVE-2018-17297
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 · uneditedThe unzip function in ZipUtil.java in Hutool before 4.1.12 allows remote attackers to overwrite arbitrary files via directory traversal sequences in a filename within a ZIP archive.
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 unzip function in Hutool's ZipUtil.java (versions before 4.1.12) lacks proper path validation when extracting files from ZIP archives. Attackers can embed directory traversal sequences (e.g., ../../../etc/passwd) in filenames within a crafted ZIP file, causing files to be extracted outside the intended target directory and potentially overwriting system files.
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< 4.1.12CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify the installed Hutool versionCheck your project's dependency management file (Maven pom.xml, Gradle build.gradle, or similar) for the hutool-all or hutool-zip artifact version, or run 'mvn dependency:tree' or 'gradle dependencies' to list the resolved versionAffected if The version listed is less than 4.1.12 (for example, 4.1.11, 4.1.10, etc.)
-
Confirm ZipUtil is in useSearch your codebase for imports of cn.hutool.core.util.ZipUtil and calls to methods such as unzip, unzipFile, or zip unarchiving operationsAffected if Code uses ZipUtil for extracting ZIP archives
-
Identify ZIP file sourcesReview the code that calls ZipUtil.unzip() or related methods to determine if ZIP files come from untrusted sources (user uploads, network downloads, external APIs, or any source outside your trust boundary)Affected if ZIP files from untrusted sources are being extracted using ZipUtil
-
Check for custom path validationSearch your codebase for path validation logic that sanitizes or validates entry names before extraction (look for checks using contains, startsWith, normalize, or similar path manipulation on zip entry names)Affected if No custom path validation exists and the Hutool version is below 4.1.12
-
Inspect extraction destinationExamine the target directory parameter passed to ZipUtil.unzip() calls to determine the intended extraction location and whether it has write access to sensitive system directoriesAffected if Extraction target is a directory with elevated privileges or system-wide paths
You are affected if your Hutool version is below 4.1.12 and you use ZipUtil to extract ZIP files, particularly from untrusted sources, without additional path validation logic.
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 data4.1.12
Upgrade Hutool to version 4.1.12 or later, which implements proper path validation to prevent directory traversal during extraction. If upgrade is not possible, implement manual path validation before file extraction.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17297 — 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-17297 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