CVE-2018-16170
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 Remote Service 3.0.0 to 3.1.8 for Windows allows remote authenticated attackers to read arbitrary files via unspecified vectors.
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 confidenceDirectory traversal vulnerability in Cybozu Remote Service versions 3.0.0 through 3.1.8 on Windows allows remote authenticated attackers to read arbitrary files on the host system by manipulating file path inputs to traverse beyond 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>= 3.0.0, <= 3.1.8CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify if Cybozu Remote Service is installedCheck the Windows system for Cybozu Remote Service installation. Look for the service in Windows Services (services.msc), or check common installation paths such as C:\Program Files\Cybozu or C:\Program Files (x86)\Cybozu for the Remote Service Manager component.Affected if The Cybozu Remote Service Manager service is found on the system
-
Determine the installed version numberLocate the version information for Cybozu Remote Service Manager. In Windows, right-click the executable or access it via the Windows Programs and Features control panel, or check the version property of the service executable.Affected if The installed version falls within the range 3.0.0 through 3.1.8 (inclusive)
-
Verify if remote access functionality is enabledConfirm that the Cybozu Remote Service is configured to accept remote connections. Check the service configuration settings or administration console to determine if remote file access or file serving features are enabled.Affected if Remote access or file-serving features are enabled and accessible to remote users
-
Confirm network exposure of the serviceDetermine if the Cybozu Remote Service is listening on network ports or accessible from remote systems. Check firewall rules, listening ports, or the service binding configuration.Affected if The service is exposed to network access from untrusted or external networks
A user is affected if Cybozu Remote Service Manager version 3.0.0 through 3.1.8 is installed with remote file-serving features enabled and network accessibility configured.
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 Cybozu Remote Service to a version beyond 3.1.8, or apply any vendor-provided security patches. If upgrades are not immediately feasible, implement strict input validation and whitelist-based path checking on all file-serving endpoints to prevent path traversal sequences.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16170 — 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-16170 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