CVE-2018-0704
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 Office 10.0.0 to 10.8.1 allows remote attackers to delete arbitrary files via Keitai Screen.
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 exists in Cybozu Office versions 10.0.0 through 10.8.1. The flaw resides in the Keitai Screen (mobile interface) component, which fails to properly sanitize file path inputs. Remote attackers can manipulate path traversal sequences (e.g., ../../) to delete arbitrary files on the server filesystem outside the intended directory boundaries.
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>= 10.0.0, <= 10.8.1CVSS 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.
-
Confirm Cybozu Office installationIdentify whether Cybozu Office is installed on the system by checking for the application in your installed programs list or by accessing the web application login page.Affected if Cybozu Office is installed and accessible on the network
-
Determine installed versionCheck the installed Cybozu Office version through the administration panel, system information page, or by reviewing installation documentation. Compare the version number against the affected range 10.0.0 to 10.8.1.Affected if The installed version falls within 10.0.0 through 10.8.1
-
Verify Keitai Screen is accessibleDetermine whether the Keitai Screen (mobile interface) component is enabled and accessible. This is typically accessed via mobile device access to the Cybozu Office URL or through the mobile settings panel in the administration console.Affected if Keitai Screen functionality is enabled and reachable over the network
-
Check for unauthenticated path accessReview access logs and web server logs for suspicious requests containing path traversal sequences such as ../ or ../../ directed at the mobile interface endpoints.
You are affected if Cybozu Office version 10.0.0 through 10.8.1 is installed and the Keitai Screen mobile interface component is enabled and accessible on your 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.
From vendor dataApply the vendor patch from Cybozu to upgrade to a patched version. If immediate patching is not possible, restrict network access to the Keitai Screen functionality through firewall rules or disable the feature until the patch can be applied.
- 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-0704 — 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-0704 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