CVE-2018-1884
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 · uneditedIBM Case Manager 5.2.0.0, 5.2.0.4, 5.2.1.0, 5.2.1.7, 5.3.0.0, and 5.3.3.0 is vulnerable to a "zip slip" vulnerability which could allow a remote attacker to execute code using directory traversal techniques. IBM X-Force ID: 151970.
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 confidenceIBM Case Manager versions 5.2.0.0 through 5.3.3.0 are vulnerable to a 'zip slip' directory traversal vulnerability during archive extraction. An attacker can craft a malicious zip file containing entries with '../' path traversal sequences in filenames, causing files to be extracted outside the intended directory, potentially overwriting system files or placing executable code in web-accessible directories.
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= 5.2.0.0= 5.2.0.4= 5.2.1.0= 5.2.1.7= 5.3.0.0= 5.3.3.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify IBM Case Manager installationCheck for IBM Case Manager installation by looking for its installation directory (typically under /opt/ibm or C:\Program Files\IBM), or query installed applications via system package manager or Windows registry.Affected if IBM Case Manager is found on the system
-
Determine installed versionLocate the IBM Case Manager version information - check the installation directory for version files, the About page in the Case Manager administration console, or use the IBM Installation Manager to list installed packages.Affected if The installed version matches any of: 5.2.0.0, 5.2.0.4, 5.2.1.0, 5.2.1.7, 5.3.0.0, 5.3.3.0, or falls within the range 5.2.0.0 through 5.3.3.0
-
Identify zip archive extraction functionalityReview IBM Case Manager configuration and features to determine if any component handles zip archive uploads or extractions - this may include Case Manager Builder, content archiving features, or document import functions.Affected if Zip archive extraction capability is present and accessible to users
-
Audit access to archive upload featuresExamine user roles and permissions in IBM Case Manager to determine which users can upload or import files that the system will extract.Affected if Users with limited or untrusted privileges can upload archives that get extracted by the system
The environment is affected if IBM Case Manager version 5.2.0.0 through 5.3.3.0 is installed and the system has functionality that processes user-supplied zip archives for extraction.
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 dataApply the IBM security patch for CVE-2018-1884 to upgrade to a fixed version of IBM Case Manager. If a patch is unavailable, disable or restrict the ability to upload and extract zip archives until remediation is possible.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1884 — 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-1884 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