CVE-2022-27925
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 · uneditedZimbra Collaboration (aka ZCS) 8.8.15 and 9.0 has mboximport functionality that receives a ZIP archive and extracts files from it. An authenticated user with administrator rights has the ability to upload arbitrary files to the system, leading to directory traversal.
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 confidenceZimbra Collaboration's mboximport functionality allows authenticated administrators to upload ZIP archives that are extracted on the server. The vulnerability enables directory traversal during extraction, permitting attackers to write arbitrary files to locations outside the intended upload directory.
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= 8.8.15= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zimbra versionRun 'zmcontrol -v' or check the installed packages using the system package manager to determine the exact version of Zimbra Collaboration Suite installedAffected if The installed version is exactly 8.8.15 or exactly 9.0.0 (no patches applied)
-
Confirm administrative access is enabledVerify that the Zimbra administrative interface (port 7071) or admin web portal is accessible and operationalAffected if The admin interface is accessible, indicating the attack surface exists for authenticated administrator access
-
Check mboximport functionality statusUse zmprov to query whether the mboximport service is available, or examine the Zimbra admin console for the import/backup features accessible to administratorsAffected if The mboximport feature is enabled and accessible to authenticated administrators, which is the required vector for this vulnerability
-
Review administrator accounts and accessList all administrator accounts using 'zmprov -l gaa' and review recent admin login activity in audit logs to identify unauthorized or suspicious admin accessAffected if Any administrator account exists and can access the admin interface, creating potential for exploitation
-
Examine import activity logsReview Zimbra mail log files and audit logs for any mboximport or zip extraction operations that may indicate exploitation attemptsAffected if Any mboximport operations involving ZIP archives are present in logs, particularly those with unusual path traversal patterns
You are affected if your Zimbra installation is version 8.8.15 or 9.0.0 and the administrative interface with mboximport functionality is accessible to any authenticated administrator.
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 · scopedApply the vendor-released security patch for CVE-2022-27925 to affected ZCS 8.8.15 and 9.0 installations. Additionally, restrict administrative access and monitor mboximport operations for suspicious activity until patching is complete.
Zimbra 8.8.15 P32 or Zimbra 9.0.0 P31 (or later stable releases)
- 1. Identify the currently installed Zimbra Collaboration Suite version (8.8.15 or 9.0.0) using 'zmcontrol -v' as the zimbra user.
- 2. For Zimbra 8.8.15: Upgrade to Patch 32 (8.8.15 P32) or later by applying the official Zimbra patch.
- 3. For Zimbra 9.0.0: Upgrade to Patch 31 (9.0.0 P31) or later by applying the official Zimbra patch.
- 4. Download the appropriate patch from the official Zimbra support portal (https://www.zimbra.com/download/) or Zimbra packaging repositories.
- 5. Run the installation as the zimbra user following Zimbra's standard patch installation procedure.
- 6. Verify the patch was applied successfully by checking the version and reviewing /opt/zimbra/.install_history if available.
- 7. Restart Zimbra services using 'zmcontrol restart' to ensure all components are running with the patched code.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27925 — 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-2022-27925 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