CVE-2018-0705
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 · uneditedDirectory traversal vulnerability in Cybozu Dezie 8.0.2 to 8.1.2 allows remote attackers to read arbitrary files via HTTP requests.
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 confidenceA directory traversal vulnerability in Cybozu Dezie versions 8.0.2 to 8.1.2 allows remote attackers to read arbitrary files on the server by manipulating file paths in HTTP requests, likely using '../' sequences to escape the intended directory. This is a critical remote file disclosure vulnerability with CVSS 9.1.
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>= 8.0.2, <= 8.1.2CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Verify Cybozu Dezie installation existsLocate the Cybozu Dezie installation directory on the server. Common paths include C:\Program Files\Cybozu\Dezie or /opt/cybozu/dezie on Linux systems. Check for the presence of the main executable or service.Affected if Cybozu Dezie software is installed on the system
-
Determine installed version numberCheck the version of Cybozu Dezie by examining the product's about page, version file, or service information. The version is typically displayed in the Dezie client or can be found in installation logs or registry entries on Windows.Affected if Installed version falls within 8.0.2 to 8.1.2 inclusive
-
Confirm web interface accessibilityVerify that the Cybozu Dezie web server component is running and accessible on the network. Check if the HTTP/HTTPS service is listening on the configured port (typically 8080 or 8443).Affected if The Dezie web interface is exposed and reachable via network requests
-
Identify if file download feature is enabledDetermine whether the file download or file transfer functionality within Dezie is enabled and accessible. Review the application configuration settings for any file access modules.Affected if File download or transfer functionality is available in the accessible web interface
User is affected if Cybozu Dezie version 8.0.2 through 8.1.2 is installed and the web interface with file access features is accessible on the network.
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.
dbcve · scopedUpgrade to a patched version of Cybozu Dezie; as an interim control, implement strict input validation to reject path traversal characters and consider deploying a WAF rule to block requests containing '../' patterns.
Dezie version 8.1.3 or later (any stable release beyond 8.1.2)
- 1. Identify the current Dezie installation version to confirm it falls within the vulnerable range (8.0.2 to 8.1.2)
- 2. Back up all existing data and configurations before proceeding with any upgrade
- 3. Obtain the latest stable release of Cybozu Dezie from official Cybozu distribution channels
- 4. Upgrade the Dezie installation to the fixed release (version 8.1.3 or later)
- 5. Verify the upgrade was successful by checking the application version
- 6. Test that the directory traversal vulnerability is no longer exploitable
- 7. Monitor application logs for any suspicious access attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0705 — 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-0705 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