dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2024-45512

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-21
Fix available
A fix is available. Upgrade to 9.0.0 / 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 webmail in Zimbra Collaboration (ZCS) through 10.1. An attacker can exploit this vulnerability by creating a folder in the Briefcase module with a malicious payload and sharing it with a victim. When the victim interacts with the folder share notification, the malicious script executes in their browser. This stored Cross-Site Scripting (XSS) vulnerability can lead to unauthorized actions within the victim's session.

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 stored Cross-Site Scripting (XSS) vulnerability exists in Zimbra Collaboration Suite (ZCS) webmail's Briefcase module through version 10.1. An authenticated attacker can create a folder with a malicious script payload in the Briefcase and share it with a victim. When the victim interacts with the share notification, the stored JavaScript executes in their browser context, potentially allowing session hijacking or unauthorized actions.

MitigationImplement server-side input validation and output encoding for folder names in the Briefcase module, particularly in share notification rendering. Consider Content Security Policy (CSP) headers to mitigate XSS execution. Apply any vendor-supplied patches for ZCS 10.1.

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.0, < 10.0.9= 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
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. Identify ZCS version
    Check the installed Zimbra Collaboration Suite version using thezmcontrol command (zmcontrol -v) or by examining the ZCS package installed on the server
    Affected if The installed version is < 9.0.0, = 9.0.0, >= 10.0.0 and < 10.0.9, or = 10.1.0
  2. Verify Briefcase module is enabled
    Confirm the Briefcase feature is active for user accounts by checking the ZCS administrative console or looking for Briefcase-related configuration in the server settings
    Affected if Briefcase module is enabled and accessible to users
  3. Inspect Briefcase folders for suspicious names
    Review existing Briefcase folder names for any that contain HTML or script tags, unusual encoding, or unexpected characters. Access this via the webmail interface or by querying the ZCS database for folder entries in the Briefcase
    Affected if Any folder name contains raw HTML tags, JavaScript event handlers, or encoded script payloads
  4. Review share notifications for XSS vectors
    Examine share notification records in the ZCS database or mail queue for any that contain unsanitized folder names or unexpected script content in notification messages
    Affected if Share notifications contain unescaped HTML or JavaScript in folder share metadata

You are affected if your ZCS version falls within the vulnerable ranges AND the Briefcase module is enabled, particularly if any Briefcase folders have been shared with notifications containing unsanitized content.

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 9.0.0 / 10.0.9 or later
Fixed in 9.0.010.0.9
Interim mitigation

Implement server-side input validation and output encoding for folder names in the Briefcase module, particularly in share notification rendering. Consider Content Security Policy (CSP) headers to mitigate XSS execution. Apply any vendor-supplied patches for ZCS 10.1.

Recommended fix Moderate confidence

ZCS 10.0.9+ or 10.1.1+ (or latest 9.0.x patch for 9.x installations)

  1. 1. Identify the current Zimbra Collaboration Suite version by running: zmcontrol -v or checking the admin console
  2. 2. For ZCS 10.0.x installations: Upgrade to version 10.0.9 or later which contains the security fix for this vulnerability
  3. 3. For ZCS 10.1.0 installations: Upgrade to version 10.1.1 or later
  4. 4. For ZCS 9.0.0 installations: Upgrade to version 9.0.1 or the latest 9.0.x patch
  5. 5. For any ZCS versions < 9.0.0: Plan migration to a supported version (9.0.1+ or 10.0.9+/10.1.1+)
  6. 6. After upgrade, verify the Briefcase module functionality works correctly and the XSS fix is applied
  7. 7. Review admin audit logs to check for any prior exploitation attempts
Caveat Review Zimbra compatibility matrix before upgrading; ensure third-party Zimbra extensions are compatible with target version; test in staging environment first

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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