dbcve.org
CollaborationApplication · Zimbra

CVE-2022-45912

HIGH · 7.2 CVSS v3.1 Published 2022-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Zimbra Collaboration (ZCS) 8.8.15 and 9.0. Remote code execution can occur through ClientUploader by an authenticated admin user. An authenticated admin user can upload files through the ClientUploader utility, and traverse to any other directory for remote code execution.

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

Zimbra Collaboration Suite contains a path traversal vulnerability in the ClientUploader component. An authenticated administrator can upload files through the utility and use directory traversal to write malicious files to arbitrary system directories, achieving remote code execution.

MitigationApply vendor patches for CVE-2022-45912 or upgrade to a patched ZCS version. Alternatively, restrict admin access and disable or limit ClientUploader functionality until patching is possible.

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:= 8.8.15= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 installed version
    Run 'zmcontrol -v' or check the Zimbra version file to determine the exact installed version of Zimbra Collaboration Suite
    Affected if The installed version is exactly 8.8.15 or exactly 9.0.0
  2. Verify ClientUploader component status
    Check if the ClientUploader web endpoint is accessible and enabled on the Zimbra server. This is typically found under the /service/extension/clientuploader/ path
    Affected if ClientUploader is enabled and accessible without additional restrictions
  3. Confirm admin console accessibility
    Verify that the Zimbra admin console (/zimbraAdmin/) is reachable and authentication is possible for administrator accounts
    Affected if Admin console is accessible and administrators can authenticate
  4. Check for suspicious uploaded files
    Inspect directories outside the expected upload path for newly created files, particularly in system directories like /opt/zimbra/ or /tmp/. Review access logs for ClientUploader requests with traversal patterns (e.g., ../../../)
    Affected if Unusual files exist in system directories or logs show traversal patterns in ClientUploader requests

The environment is affected if ZCS version is exactly 8.8.15 or 9.0.0, ClientUploader is enabled, and an attacker with admin access could exploit the path traversal to write arbitrary files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for CVE-2022-45912 or upgrade to a patched ZCS version. Alternatively, restrict admin access and disable or limit ClientUploader functionality until patching is possible.

Recommended fix Moderate confidence

Zimbra Collaboration 9.0.1 or later / Zimbra Collaboration 8.8.15 Patch 30 or later

  1. Identify your current Zimbra Collaboration version by running: zmcontrol -v
  2. Download and apply the latest Zimbra Collaboration 9.0.0 patch (Patch 30 or later) from the Zimbra support portal or package repositories
  3. Alternatively, upgrade to Zimbra Collaboration 9.0.1 or later which includes the fix for CVE-2022-45912
  4. After applying the patch or upgrade, verify the ClientUploader endpoint no longer allows directory traversal by testing with a path traversal payload in the upload parameter
  5. Ensure admin access is restricted to trusted users and implement the principle of least privilege for admin accounts
Caveat Major version upgrades may require migration planning; test in staging first

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

Fix this in Collaboration 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 help mitigating

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-2022-45912 — 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-2022-45912 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