CVE Tools

CVE-2024-45519

Exploited in the wild. In CISA KEV since 2024‑10‑03. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check your Zimbra Collaboration Suite version and whether your installation is earlier than 8.8.15 Patch 46, 9.0.0 Patch 41, 10.0.9, or 10.1.1.
  2. Upgrade Zimbra Collaboration Suite to 8.8.15 (Patch 46), 9.0.0 (Patch 41), 10.0.9, or 10.1.1.
  3. If you cannot upgrade immediately, stop exposing the Zimbra postjournal service to the public internet and follow Zimbra’s mitigation guidance for this issue.
  4. Verify the post-upgrade version, then review server logs for any suspicious postjournal-related requests around the timeframe of the vulnerability exposure.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

Zimbra Collaboration (ZCS) has a critical bug in its postjournal service that can let an attacker run commands on the server without logging in. If your business runs ZCS and it’s not updated to the listed fixes, you should treat this as urgent.

CVE-2024-45519 is an unauthenticated command-execution flaw in the Zimbra Collaboration Suite (ZCS) postjournal service; attackers can send a network request that triggers unauthorized system command execution on a vulnerable server.

If you're affected

  • Full server takeover
  • Disruption of email service
  • Data theft risk
  • Malware/ransomware risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2024-10-03.

US federal agencies must remediate by 2024-10-24.

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

100% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 631 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Nuclei check added
  3. Patch availablerecord updated
  4. Added to CISA KEV
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Synacor, not every advisory. This one: actively exploited.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store