dbcve.org
CollaborationApplication · Zimbra

CVE-2024-33533

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 10.0.8 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) 9.0 and 10.0, issue 1 of 2. A reflected cross-site scripting (XSS) vulnerability has been identified in the Zimbra webmail admin interface. This vulnerability occurs due to inadequate input validation of the packages parameter, allowing an authenticated attacker to inject and execute arbitrary JavaScript code within the context of another user's browser session. By uploading a malicious JavaScript file and crafting a URL containing its location in the packages parameter, the attacker can exploit this vulnerability. Subsequently, when another user visits the crafted URL, the malicious JavaScript code is executed.

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 reflected cross-site scripting (XSS) vulnerability exists in the Zimbra webmail admin interface due to insufficient input validation of the packages parameter. An authenticated attacker can upload a malicious JavaScript file, then craft a URL containing its location in the packages parameter. When other users visit this crafted URL, the malicious JavaScript executes within their browser session context.

MitigationImplement strict input validation and output encoding on the packages parameter in the admin interface to prevent injection of malicious scripts. Consider implementing Content Security Policy headers as a defense-in-depth measure.

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
CollaborationApplication
Affected:>= 10.0.0, < 10.0.8= 9.0.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 Zimbra Collaboration version
    Run 'zmcontrol -v' as the zimbra user, or check /opt/zimbra/.release file, or view the version displayed in the admin console login page
    Affected if Version is 9.0.0, or version is 10.0.0 through 10.0.7 (any version >= 10.0.0 but < 10.0.8)
  2. Determine if admin interface is network-accessible
    Check the Zimbra proxy configuration and firewall rules to see if the admin interface (typically port 7071 or through the web mail server on port 443) is reachable from untrusted networks
    Affected if The admin interface is exposed to network segments where untrusted users could access it
  3. Verify authentication controls on admin interface
    Review Zimbra's admin console access controls in /opt/zimbra/conf/nginx/conf.d/ and confirm that admin access requires valid authentication
    Affected if The admin interface permits authenticated access without additional input validation on the packages parameter
  4. Confirm packages parameter handling in admin interface
    If you have access to the admin interface, navigate to the area where the packages parameter is used (related to package management features) and inspect whether user-supplied input in the packages parameter is reflected in the response without proper encoding
    Affected if The packages parameter in the admin interface accepts and reflects unsanitized input in HTTP responses

You are affected if your Zimbra Collaboration version is 9.0.0 or any version from 10.0.0 through 10.0.7 AND the admin interface is accessible to users who could inject malicious content into the packages parameter.

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.8 or later
Fixed in 10.0.8
Interim mitigation

Implement strict input validation and output encoding on the packages parameter in the admin interface to prevent injection of malicious scripts. Consider implementing Content Security Policy headers as a defense-in-depth measure.

Recommended fix High confidence

Zimbra Collaboration 10.0.8 or later (10.x branch); contact vendor for 9.x patch/upgrade path

  1. 1. Upgrade Zimbra Collaboration version 10.0.x to version 10.0.8 or later
  2. 2. For Zimbra 9.0.0, apply vendor-supplied patch or upgrade to a patched version (contact Zimbra support for specific 9.x patch availability)
  3. 3. After upgrading, verify the packages parameter is properly sanitized in the admin interface
  4. 4. Confirm the XSS vulnerability is resolved by testing that the packages parameter no longer executes injected JavaScript
Caveat Review Zimbra 10.0.8 release notes for any configuration or feature changes that may require adjustments

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

Fix this in Collaboration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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