dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2024-45517

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-21
Fix available
A fix is available. Upgrade to 8.8.15 / 10.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Zimbra Collaboration (ZCS) through 10.1. A Cross-Site Scripting (XSS) vulnerability in the /h/rest endpoint of the Zimbra webmail and admin panel interfaces allows attackers to execute arbitrary JavaScript in the victim's session. This issue is caused by improper sanitization of user input, leading to potential compromise of sensitive information. Exploitation requires user interaction to access the malicious URL.

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

A reflected Cross-Site Scripting (XSS) vulnerability in the /h/rest endpoint of Zimbra Collaboration Suite (through version 10.1) allows attackers to inject arbitrary JavaScript via improperly sanitized user input. Successful exploitation enables session hijacking and sensitive data theft through the victim's browser, requiring user interaction (clicking a malicious URL).

MitigationApply vendor-provided patches for ZCS 10.1 or later; until then, implement output encoding and input validation on the /h/rest endpoint and consider restricting access to the admin panel.

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.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Confirm Zimbra Collaboration Suite installation
    Check for ZCS installation by looking for Zimbra processes or examining common installation directories such as /opt/zimbra or /usr/local/zimbra
    Affected if ZCS is not present on the system, the vulnerability does not apply
  2. Identify installed ZCS version
    Run the Zimbra version command: zmcontrol -v or check the ZCS version file if accessible, such as /opt/zimbra/.version
    Affected if The installed version falls within the affected ranges: < 8.8.15, = 8.8.15, = 9.0.0, >= 10.0.0 and < 10.0.9, or = 10.1.1
  3. Verify /h/rest endpoint accessibility
    Check if the /h/rest web endpoint is exposed by attempting to access it via browser or curl: https://<server>/h/rest or examining the Zimbra proxy and web server configuration
    Affected if The endpoint is publicly or internally accessible without proper sanitization controls in place
  4. Confirm no input sanitization on /h/rest
    Inspect the application configuration or web server logs for the /h/rest endpoint to determine if output encoding or input validation is being applied to user-supplied parameters
    Affected if No input validation or output encoding is configured for the /h/rest endpoint, making exploitation possible

The environment is affected if ZCS is installed with a version matching < 8.8.15, = 8.8.15, = 9.0.0, >= 10.0.0 through < 10.0.9, or = 10.1.1 AND the /h/rest endpoint is accessible without sanitization controls in place.

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

Apply vendor-provided patches for ZCS 10.1 or later; until then, implement output encoding and input validation on the /h/rest endpoint and consider restricting access to the admin panel.

Recommended fix Moderate confidence

Zimbra 8.8.15 Patch 1+ or Zimbra 10.0.9+

  1. Identify your current Zimbra Collaboration Suite version by checking the admin console or running 'zmcontrol -v'
  2. For Zimbra 8.8.x: Upgrade to version 8.8.15 Patch 1 or later
  3. For Zimbra 10.0.x: Upgrade to version 10.0.9 or later
  4. After upgrading, verify the /h/rest endpoint no longer reflects unsanitized user input
  5. Test that legitimate webmail and admin panel functionality remains intact after the patch
Caveat Review Zimbra release notes for your specific version upgrade to check for any configuration or feature changes

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

Fix this in Zimbra Collaboration Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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