CVE-2018-0702
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 Mailwise 5.0.0 to 5.4.5 allows remote attackers to delete 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 · moderate confidenceA directory traversal vulnerability in Cybozu Mailwise versions 5.0.0 through 5.4.5 allows remote attackers to delete arbitrary files on the host system by manipulating file paths, likely through improper sanitization of path traversal sequences (..) in user-supplied input.
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>= 5.0.0, <= 5.4.5CVSS 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.
-
Identify the installed Cybozu Mailwise versionAccess the Mailwise administration console or check the software installation directory for version information. Most Cybozu products include a version display in the system settings or about page.Affected if The installed version is 5.0.0, 5.4.5, or any version between these values (5.0.0 <= version <= 5.4.5)
-
Determine if the Mailwise service is network accessibleCheck network configuration and firewall rules to verify whether the Cybozu Mailwise web interface (typically on ports 80/443 or custom ports) is exposed to untrusted networks or the internet.Affected if The Mailwise HTTP/HTTPS interface is reachable from outside the trusted internal network
-
Verify if file attachment or file management features are enabledReview Mailwise configuration settings to confirm whether features that handle file uploads, attachments, or file management are active, as these are the potential attack vectors for path traversal.Affected if File attachment handling or file management features are enabled and accessible to users
-
Review access logs for path traversal patternsExamine Mailwise server access and audit logs for requests containing sequence patterns such as '../' or '..\' in file-related parameters, which may indicate exploitation attempts.Affected if Suspicious path traversal sequences appear in logs or unusual file deletion events are recorded
A user is affected if Cybozu Mailwise version 5.0.0 through 5.4.5 is installed AND the service is accessible to potential attackers, particularly if file handling features are enabled.
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 Mailwise to version 5.4.6 or later. If immediate patching is not possible, restrict network access to the Mailwise service and implement file system permissions to limit the impact of arbitrary file deletion.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0702 — 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-0702 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