CVE-2024-33536
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 · uneditedAn issue was discovered in Zimbra Collaboration (ZCS) 9.0 and 10.0. The vulnerability occurs due to inadequate input validation of the res 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, accessible externally, and crafting a URL containing its location in the res 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 confidenceA Cross-Site Scripting (XSS) vulnerability in Zimbra Collaboration versions 9.0 and 10.0 allows authenticated attackers to inject arbitrary JavaScript code via the unvalidated res parameter. The attack vector involves uploading a malicious JavaScript file externally and crafting a URL containing its location in the res parameter, which then executes in the context of other users' browser sessions when they visit the crafted URL.
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>= 10.0.0, < 10.0.8= 9.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Zimbra Collaboration installationCheck for Zimbra by querying the web service at /zimbra/ or reviewing installed packages via package manager (dpkg -l | grep zimbra or rpm -qa | grep zimbra)Affected if Zimbra Collaboration is not installed - not affected by this CVE
-
Determine installed Zimbra versionRun zmcontrol -v as the zimbra user, or check /opt/zimbra/.install_history, or inspect the version via the Admin Console web interface under Home > Configure > Global SettingsAffected if Version is 9.0.0 or >= 10.0.0 but < 10.0.8 - potentially affected
-
Verify Zimbra web service is exposedConfirm the Zimbra web client is accessible by accessing the login page at /zimbra/ or /mail/Affected if Web interface is accessible - attack surface exists for XSS
-
Check if res parameter is present in web applicationExamine HTTP responses when accessing Zimbra endpoints and look for the res parameter handling in the application logs or source code under /opt/zimbra/jetty/webapps/zimbra/Affected if The res parameter is processed by the application - vulnerable to injection if unpatched
-
Confirm authentication mechanism is enabledVerify that Zimbra requires authentication for accessing the web client by attempting to access protected resources without credentialsAffected if Authentication is enforced - this XSS requires authenticated attackers to exploit
Your environment is affected only if Zimbra Collaboration versions 9.0.0 or 10.0.0 through 10.0.7 are installed and the web interface with the res parameter is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.8
Implement proper input validation and sanitization for the res parameter, validate that uploaded files do not contain executable content, and apply context-aware output encoding when reflecting user-supplied values in HTTP responses.
10.0.8
- 1. Back up your current Zimbra Collaboration installation and database before proceeding with any upgrade.
- 2. Verify current installed version by running: zmcontrol -v
- 3. Download Zimbra Collaboration 10.0.8 from the official Zimbra package repository or customer portal.
- 4. Ensure all prerequisites for ZCS 10.0.8 are met, including operating system version and dependencies.
- 5. Run the Zimbra installer for version 10.0.8: ./install.sh -s (or appropriate install flags for your setup)
- 6. Follow the on-screen prompts to complete the upgrade process.
- 7. After installation, verify the version: zmcontrol -v
- 8. Confirm the res parameter is now properly validated and no longer accepts malicious input.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33536 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-33536 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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