CVE-2016-3408
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 · uneditedCross-site scripting (XSS) vulnerability in Zimbra Collaboration before 8.7.0 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, aka bug 101813.
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 confidenceCross-site scripting (XSS) vulnerability in Zimbra Collaboration prior to version 8.7.0 allows remote attackers to inject arbitrary web script or HTML through unspecified vectors. The vulnerability exists in the web interface and could allow an attacker to execute malicious scripts in the context of a victim's browser session.
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.6.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Zimbra installationLocate Zimbra installation directories. Common paths include /opt/zimbra, /usr/local/zimbra, or check for 'zimbra' user and processes using 'ps aux | grep zimbra'Affected if Zimbra Collaboration Suite is not installed on the system
-
Determine installed Zimbra versionRun '/opt/zimbra/bin/zmcontrol -v' or '/opt/zimbra/libexec/zmversioninfo' to retrieve the installed version number. Alternatively, check /opt/zimbra/.install_history or /opt/zimbra/zmversionAffected if Cannot determine the version or version command is unavailable
-
Compare version against affected rangeCompare the installed version number to the affected range: versions 8.6.0 and below are vulnerable. Versions 8.7.0 and later are not affected by this CVEAffected if Installed version is 8.6.0 or lower (for example, 8.6.0, 8.5.0, 8.0.x, etc.)
-
Verify web interface is accessibleConfirm the Zimbra web interface (Zimbra Web Client) is enabled and accessible. Check via 'zmprov gs $(hostname) zimbraWebClientEnabled' or by attempting to access https://yourserver/webclientAffected if Web interface is enabled and exposed to users or network
Environment is affected if Zimbra Collaboration Suite is installed with version 8.6.0 or lower and the web interface is 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 Zimbra Collaboration to version 8.7.0 or later to address this vulnerability. As a temporary measure, implement Content Security Policy (CSP) headers and validate/sanitize user inputs in web application layers.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3408 — 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-2016-3408 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