dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2019-6981

MEDIUM · 6.5 CVSS v3.0 Published 2019-05-29
Fix available
A fix is available. Upgrade to 8.7.11 / 8.8.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Zimbra Collaboration Suite 8.7.x through 8.8.11 allows Blind SSRF in the Feed component.

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 confidence

Zimbra Collaboration Suite versions 8.7.x through 8.8.11 contains a Blind Server-Side Request Forgery (SSRF) vulnerability in the Feed component. This allows an attacker to induce the Zimbra server to make arbitrary HTTP requests to internal or external resources without seeing the full response, potentially enabling reconnaissance of internal networks or interaction with internal services.

MitigationUpgrade Zimbra to a version beyond 8.8.11 where the vulnerability is patched. Additionally, implement network segmentation and firewall rules to restrict outbound connections from the Zimbra server to only necessary endpoints.

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.8.0, < 8.8.9= 8.7.11= 8.8.9= 8.8.10= 8.8.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Identify installed Zimbra version
    Run the Zimbra version command: zmcontrol -v or check the installed packages via the package manager (rpm -q zimbra-core). Alternatively, access the Zimbra Admin Console and check the version displayed on the login page or in the About section.
    Affected if The installed version is 8.7.0 through 8.7.11, or 8.8.0 through 8.8.11 (any version from 8.7.x up to and including 8.8.11).
  2. Confirm the Feed component is accessible
    Check if the Zimbra Feed feature endpoint is available. The Feed functionality in Zimbra is typically accessed via the /service/feed/ path or through the Zimbra Web Client. Verify if this endpoint responds by making a request to the server on common ports (80/443).
    Affected if The Feed component endpoint is reachable and responds to requests on the Zimbra server.
  3. Inspect Zimbra proxy configuration
    Examine the Zimbra proxy configuration files (typically in /opt/zimbra/conf/ or via zmprov gacf) to determine if the Feed service is routed through the Zimbra proxy and therefore potentially exposed externally.
    Affected if The Zimbra proxy is configured to allow external access to the Feed component without proper restrictions.
  4. Review access logs for Feed endpoint activity
    Examine Zimbra access logs (typically located in /opt/zimbra/log/) for suspicious requests to the /service/feed/ or similar Feed-related paths, especially those making requests to internal IP addresses (10.x.x.x, 192.168.x.x, 127.x.x.x) or internal hostnames.
    Affected if Log entries show requests from the Feed endpoint to internal network addresses or unusual external destinations.

A user is affected if their Zimbra server is running version 8.7.x through 8.8.11 AND the Feed component is accessible and enabled, making the server vulnerable to induced HTTP requests to internal or external resources.

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.

From vendor data
Upgrade available Upgrade to 8.7.11 / 8.8.9 or later
Fixed in 8.7.118.8.9
Interim mitigation

Upgrade Zimbra to a version beyond 8.8.11 where the vulnerability is patched. Additionally, implement network segmentation and firewall rules to restrict outbound connections from the Zimbra server to only necessary endpoints.

Fix this in Zimbra Collaboration Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA6.0 h
48.0 hours of engineering $8,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6981 — 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-6981 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