CVE-2018-7806
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 Operation 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 Operation's zip file upload feature in Java is vulnerable to ZipSlip path traversal. An authenticated user can upload a specially crafted malicious zip file containing filenames with '../' sequences that cause files to be extracted outside the intended upload directory, achieving 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 dataall versionsCVSS 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 if Struxureware Data Center Operation is installedCheck for the application in standard installation paths such as C:\Program Files\Schneider Electric\Struxureware Data Center Operation or /opt/schneider/ on Linux. Also check running services for processes named 'Struxureware' or 'DataCenterOperation'.Affected if The product is installed and running on the system
-
Confirm the product versionLook for version information in the application's About section, installation directory, or check the service properties. Common locations include the conf/version.properties file or the application's main executable metadata.Affected if Any installed version is confirmed as Struxureware Data Center Operation (all versions are affected)
-
Verify the web service is exposedCheck if the Data Center Operation web interface port (default 8080 or configured port) is listening and accessible. Use netstat or similar tools to identify listening ports, and check firewall rules.Affected if The web interface port is open and reachable from network segments where attackers could upload files
-
Determine if authentication can be bypassed or if default credentials are in useReview the application's authentication configuration files in the conf directory. Check whether guest access or weak/default credentials are enabled that would allow an unauthenticated or low-privilege user to access the upload feature.Affected if The zip upload feature is accessible to low-privilege users, guest accounts, or uses default credentials
If Schneider Electric Struxureware Data Center Operation is installed and its web-based zip upload feature is accessible to authenticated users, the environment is vulnerable to CVE-2018-7806.
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 dataImplement strict path validation during zip extraction by canonicalizing all extracted file paths and verifying they remain within the intended target directory. Use a whitelist approach and reject any archive containing path traversal sequences.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7806 — 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-7806 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