dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2024-54663

HIGH · 7.5 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to 10.0.11 / 10.1.3 or later.
See remediation →
84/100
Remediation priority · High
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
An issue was discovered in the Webmail Classic UI in Zimbra Collaboration (ZCS) 9.0 and 10.0 and 10.1. A Local File Inclusion (LFI) vulnerability exists in the /h/rest endpoint, allowing authenticated remote attackers to include and access sensitive files in the WebRoot directory. Exploitation requires a valid auth token and involves crafting a malicious request targeting specific file paths.

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 Local File Inclusion (LFI) vulnerability in Zimbra Webmail Classic UI's /h/rest endpoint allows authenticated attackers with a valid auth token to read arbitrary sensitive files from the WebRoot directory by manipulating file path parameters in requests.

MitigationApply vendor security patches for CVE-2024-54663 immediately; if no patch is available, restrict or disable access to the /h/rest endpoint until a fix can be implemented.

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:>= 9.0.0, < 10.0.11>= 10.1.0, < 10.1.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 'zmcontrol -v' or check the Zimbra version file to determine the exact version number installed
    Affected if The installed version is >= 9.0.0 and < 10.0.11, or >= 10.1.0 and < 10.1.3
  2. Verify Classic UI is enabled
    Check the Zimbra web client configuration to confirm the Classic UI interface is active or available to users
    Affected if Classic UI is enabled and accessible to authenticated users
  3. Confirm /h/rest endpoint is accessible
    Verify the /h/rest endpoint is exposed on the Zimbra server by testing network access to the endpoint URL path
    Affected if The /h/rest endpoint responds to requests without being explicitly blocked at the network level
  4. Check authentication requirements for the endpoint
    Review Zimbra configuration to confirm whether the /h/rest endpoint requires valid authentication or if it can be accessed with minimal credentials
    Affected if Authenticated users with valid auth tokens can access the endpoint to manipulate file path parameters

The environment is affected if Zimbra version falls within the vulnerable ranges (9.0.0-10.0.10 or 10.1.0-10.1.2), Classic UI is enabled, and the /h/rest endpoint is accessible to authenticated users.

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 10.0.11 / 10.1.3 or later
Fixed in 10.0.1110.1.3
Interim mitigation

Apply vendor security patches for CVE-2024-54663 immediately; if no patch is available, restrict or disable access to the /h/rest endpoint until a fix can be implemented.

Recommended fix High confidence

ZCS 10.0.11 or ZCS 10.1.3 (depending on current major version)

  1. 1. Create a full backup of the Zimbra Collaboration Suite installation, including configuration files, mail stores, and the database
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Identify the current installed version by running: zmcontrol -v or checking /opt/zimbra/.install_history
  4. 4. For Zimbra 9.0.0 through 10.0.x versions: upgrade to ZCS 10.0.11
  5. 5. For Zimbra 10.1.0 through 10.1.2 versions: upgrade to ZCS 10.1.3
  6. 6. Obtain the upgrade packages from the official Zimbra repository or Customer Support portal
  7. 7. Run the upgrade installer as the zimbra user: ./install.sh -u (or use the appropriate method for your deployment)
  8. 8. After upgrade completes, verify all services are running: zmcontrol status
Caveat Review Zimbra release notes for the target version for any configuration or feature changes before upgrading

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

Fix this in Zimbra Collaboration Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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