CVE-2018-10950
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 · uneditedmailboxd in Zimbra Collaboration Suite 8.8 before 8.8.8; 8.7 before 8.7.11.Patch3; and 8.6 before 8.6.0.Patch10 allows Information Exposure through Verbose Error Messages containing a stack dump, tracing data, or full user-context dump.
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 confidenceThe mailboxd component in Zimbra Collaboration Suite versions 8.8 before 8.8.8, 8.7 before 8.7.11.Patch3, and 8.6 before 8.6.0.Patch10 contains a vulnerability where verbose error messages expose sensitive information including stack traces, tracing data, and full user-context dumps. This information disclosure could aid attackers in understanding the application's internal structure and potentially identifying further vulnerabilities.
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.7.0, < 8.7.11>= 8.8.0, < 8.8.8= 8.6.0= 8.7.11CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Zimbra Collaboration Suite versionRun 'zmcontrol -v' or check the Zimbra version via the admin console, or inspect the output of 'cat /opt/zimbra/.version_info' if presentAffected if The installed version falls within 8.6.0, 8.7.0 through 8.7.11, or 8.8.0 through 8.8.7 (i.e., not 8.8.8, 8.7.11.Patch3, or 8.6.0.Patch10)
-
Confirm mailboxd component is in useVerify that the mailboxd service is running via 'zmcontrol status' or by checking for processes related to the Zimbra mailbox service (mailboxd, Java processes with mailboxd in the command line)Affected if Mailboxd is active and serving requests
-
Examine error responses for information leakageTrigger an error condition in the mailboxd component (such as submitting malformed requests or examining existing error logs) and inspect whether the returned error messages contain stack traces, Java class names, or detailed debugging outputAffected if Error responses include stack traces, internal class names, or verbose debugging information rather than generic error messages
The environment is affected if Zimbra Collaboration Suite version is 8.6.0, 8.7.0-8.7.11, or 8.8.0-8.8.7 AND the mailboxd component is exposed, with verbose error details visible in responses or logs.
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 data8.7.118.8.8
Apply the appropriate Zimbra patch (8.8.8, 8.7.11.Patch3, or 8.6.0.Patch10) to the affected Zimbra Collaboration Suite installation to disable verbose error messaging in the mailboxd component.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10950 — 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-10950 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