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 24 Oct 2024.
Zimbra Collaboration SuiteApplication · Synacor

CVE-2024-45519

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-02
Fix available
A fix is available. Upgrade to 8.8.15 / 10.0.9 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges 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
The postjournal service in Zimbra Collaboration (ZCS) before 8.8.15 Patch 46, 9 before 9.0.0 Patch 41, 10 before 10.0.9, and 10.1 before 10.1.1 sometimes allows unauthenticated users to execute commands.

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

A command injection vulnerability in Zimbra Collaboration's postjournal service allows unauthenticated remote attackers to execute arbitrary operating system commands on the affected server. The 'sometimes' qualifier suggests specific conditions must be met for exploitation, but the critical CVSS 9.8 rating indicates successful exploitation is highly probable when conditions align.

MitigationUpdate Zimbra Collaboration to version 8.8.15 Patch 46, 9.0.0 Patch 41, 10.0.9, or 10.1.1 (or later) to remediate this vulnerability. Apply the appropriate patch immediately given the critical severity and unauthenticated attack vector.

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.8.15>= 10.0.0, < 10.0.9= 8.8.15= 9.0.0= 10.1.0

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. Verify Zimbra Collaboration Suite is installed
    Check for Zimbra installation directory: ls -la /opt/zimbra or run command: /opt/zimbra/bin/zmcontrol -v
    Affected if The system does not have Zimbra installed, then it is not affected by this CVE.
  2. Determine the installed ZCS version
    Run: /opt/zimbra/bin/zmcontrol -v or inspect: cat /opt/zimbra/.version_info
    Affected if The displayed version falls within the affected ranges: any 8.8.15 version, 9.0.0, 10.0.0 through 10.0.8, or 10.1.0.
  3. Confirm the postjournal service is enabled
    Run: /opt/zimbra/bin/zmprov gs $(hostname) zimbraServiceEnabled | grep -i postjournal, or check service status via: /opt/zimbra/bin/zmcontrol status | grep postjournal
    Affected if The postjournal service is listed as enabled or running - the command injection can be exploited.
  4. Check if postjournal is exposed to network
    Verify postjournal listens on network ports: netstat -tlnp | grep postjournal or ss -tlnp | grep postjournal. Also check firewall rules for port 10025 (default postjournal port).
    Affected if The postjournal service is bound to a network interface accessible to unauthenticated attackers.

A user is affected if they run a vulnerable ZCS version (8.8.15 any patch, 9.0.0 any patch, 10.0.0-10.0.8, or 10.1.0) AND have the postjournal service enabled and network-accessible.

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.8.15 / 10.0.9 or later
Fixed in 8.8.1510.0.9
Interim mitigation

Update Zimbra Collaboration to version 8.8.15 Patch 46, 9.0.0 Patch 41, 10.0.9, or 10.1.1 (or later) to remediate this vulnerability. Apply the appropriate patch immediately given the critical severity and unauthenticated attack vector.

Recommended fix High confidence

8.8.15 Patch 46 / 9.0.0 Patch 41 / 10.0.9 / 10.1.1 or later (latest respective release)

  1. Identify current Zimbra version by running 'zmcontrol -v' or checking the /opt/zimbra/.version file
  2. Backup the Zimbra mailbox and configuration data before proceeding with any upgrade
  3. For ZCS 8.8.x: Upgrade to 8.8.15 Patch 46 or later
  4. For ZCS 9.0.x: Upgrade to 9.0.0 Patch 41 or later
  5. For ZCS 10.0.x: Upgrade to 10.0.9 or later
  6. For ZCS 10.1.x: Upgrade to 10.1.1 or later
  7. After upgrade, verify the postjournal service is running: 'zmcontrol status'
  8. Confirm the vulnerability is patched by checking Zimbra security advisories or running the Postjournal service health checks
Caveat Upgrading between major versions (e.g., 9.x to 10.x) may require migration steps; review Zimbra migration documentation; test upgrade in staging environment first

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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