CVE-2018-7807
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 · uneditedData Center Expert, versions 7.5.0 and earlier, allows for the upload of a zip file from its user interface to the server. A carefully crafted, malicious file could be mistakenly uploaded by an authenticated user via this feature which could contain path traversal file names. As such, it could allow for the arbitrary upload of files contained with the zip onto the server file system outside of the intended directory. This is leveraging the more commonly known ZipSlip vulnerability within Java code.
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 confidenceData Center Expert versions 7.5.0 and earlier contain a ZipSlip vulnerability where authenticated users can upload malicious zip files containing path traversal filenames (e.g., ../../../etc/passwd). When the application extracts these files, they are written outside the intended upload directory, enabling arbitrary file write on the server.
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<= 7.5.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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.
-
Identify the installed version of Struxureware Data Center ExpertLocate the application version through the web interface (typically in Help > About or System > Information), command-line interface, or installation metadata files. Compare the version number against the affected range (<= 7.5.0).Affected if The installed version is 7.5.0 or any earlier version.
-
Determine if user authentication is enabled and activeCheck whether the application requires login for access. Verify if local or remote user accounts (local, LDAP, or Active Directory) are configured and can authenticate to the Data Center Expert interface.Affected if Authentication is enabled and users can log in, as this vulnerability requires an authenticated session to upload files.
-
Identify if file upload functionality exists for authenticated usersReview the application features available to authenticated users. Look for file import, backup restore, firmware upload, report import, or any feature that accepts zip file uploads from users.Affected if Authenticated users have access to any feature that accepts and processes zip file uploads.
-
Inspect the file system for unexpected files outside upload directoriesExamine common system directories that could be targets of path traversal (e.g., /tmp, /var, /home, application root directories) for newly created or modified files that should not exist there. Compare against known-good file state or baseline.Affected if Files exist in directories outside the intended upload/extraction directory, especially system files or configuration files.
-
Review application and system logs for suspicious archive extraction eventsSearch application logs, system logs, and web server logs for patterns indicating zip file extraction with path traversal sequences (such as '../' or '..\') or extraction to unexpected directories.Affected if Logs show extraction of zip entries containing path traversal characters or extraction to directories outside the intended upload folder.
You are affected if Struxureware Data Center Expert version 7.5.0 or earlier is installed, authentication is enabled, and authenticated users can upload and extract zip files through any application feature.
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 to a patched version if available, or implement strict validation of zip entry paths using canonical path resolution to ensure extracted files remain within the intended directory before any file write operations.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7807 — 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-7807 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