dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Jul 2022.
Zimbra Collaboration SuiteApplication · Synacor

CVE-2019-9670

CRITICAL · 9.8 CVSS v3.1 Published 2019-05-29
Fix available
A fix is available. Upgrade to 8.7.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
mailboxd component in Synacor Zimbra Collaboration Suite 8.7.x before 8.7.11p10 has an XML External Entity injection (XXE) vulnerability, as demonstrated by Autodiscover/Autodiscover.xml.

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 confidence

An XML External Entity (XXE) injection vulnerability exists in the mailboxd component of Zimbra Collaboration Suite 8.7.x (before 8.7.11p10). The vulnerability is exploitable through the Autodiscover/Autodiscover.xml endpoint, allowing unauthenticated remote attackers to potentially read sensitive files from the server or perform SSRF attacks.

MitigationUpgrade to Zimbra Collaboration Suite 8.7.11p10 or later, or apply the vendor-supplied patch to remediate the XXE vulnerability in the Autodiscover functionality.

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
Zimbra Collaboration SuiteApplication
Affected:>= 8.7.0, < 8.7.11= 8.7.11

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Zimbra Collaboration Suite version
    Run 'zmcontrol -v' or check '/opt/zimbra/.install_history' to identify the installed ZCS version
    Affected if Installed version is 8.7.0 through 8.7.11 (including 8.7.11 itself), meaning version is >= 8.7.0 and < 8.7.11p10, or equals exactly 8.7.11
  2. Verify mailboxd service is running
    Run 'zmcontrol status | grep mailboxd' or 'su - zimbra -c "zmcontrol status"' to confirm the mailboxd service is active
    Affected if mailboxd service is running on an affected ZCS version
  3. Confirm Autodiscover endpoint is accessible
    Check if the Autodiscover servlet is enabled by examining the Zimbra LDAP configuration: 'ldapsearch -x -H ldap://localhost:389 -D "cn=config" -W "cn=zimbra,cn=acces,cn=zimbra"' or verify the Autodiscover.xml endpoint responds at /autodiscover/Autodiscover.xml
    Affected if The Autodiscover endpoint is accessible and responds to requests
  4. Check if XML external entity processing can be tested
    Send a crafted XXE payload to the Autodiscover/Autodiscover.xml endpoint using curl: 'curl -X POST http://localhost:8080/service/autodiscover/Autodiscover.xml -d "<?xml version=\"1.0\"?><!DOCTYPE foo [<!ENTITY xxe SYSTEM \"file:///etc/passwd\">]><Autodiscover>&xxe;</Autodiscover>"'
    Affected if The server processes the XML and returns content from local files (indicating XXE is exploitable)

A system is affected if it runs Zimbra Collaboration Suite version 8.7.0 through 8.7.11 (including 8.7.11) with mailboxd running and the Autodiscover endpoint accessible, allowing XXE injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.7.11 or later
Fixed in 8.7.11
Vendor patch bugzilla.zimbra.com →
Interim mitigation

Upgrade to Zimbra Collaboration Suite 8.7.11p10 or later, or apply the vendor-supplied patch to remediate the XXE vulnerability in the Autodiscover functionality.

Recommended fix High confidence

Zimbra Collaboration Suite 8.7.11p10 or later (8.8.x and 9.x branches also contain the fix)

  1. Confirm current Zimbra Collaboration Suite version by running: zmcontrol -v
  2. Create a full backup of the Zimbra mailboxd data and configuration before proceeding with any upgrade
  3. Download Zimbra Collaboration Suite 8.7.11p10 or later from the official Zimbra download portal
  4. Stop Zimbra services using: zmcontrol stop
  5. Apply the upgrade following Zimbra's standard upgrade documentation for your operating system
  6. After upgrade completes, start Zimbra services using: zmcontrol start
  7. Verify the mailboxd component is running properly: zmcontrol status
  8. Test that the Autodiscover/Autodiscover.xml endpoint is functioning without XXE vulnerability
Caveat Patch releases like p10 typically include bug fixes with minimal breaking changes, but always review Zimbra release notes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zimbra Collaboration Suite Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-9670 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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