CVE-2024-27442
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 zmmailboxdmgr binary, a component of ZCS, is intended to be executed by the zimbra user with root privileges for specific mailbox operations. However, an attacker can escalate privileges from the zimbra user to root, because of improper handling of input arguments. An attacker can execute arbitrary commands with elevated privileges, leading to local privilege escalation.
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 confidenceThe zmmailboxdmgr binary in Zimbra Collaboration 9.0 and 10.0 suffers from improper input argument handling, allowing a local attacker with zimbra user privileges to execute arbitrary commands with root privileges through the binary's elevated permissions, achieving local privilege escalation.
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.7= 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Collaboration versionRun: zmcontrol -v or 查看 /opt/zimbra/.zimbra_version 文件Affected if Version is 9.0.0 OR between 10.0.0 and 10.0.6 inclusive (any version < 10.0.7)
-
Locate the zmmailboxdmgr binaryRun: which zmmailboxdmgr 或 ls -la /opt/zimbra/bin/zmmailboxdmgrAffected if Binary exists at /opt/zimbra/bin/zmmailboxdmgr
-
Check sudo permissions for zimbra user on zmmailboxdmgrRun: sudo -l -U zimbra 2>/dev/null | grep zmmailboxdmgrAffected if zmmailboxdmgr appears in sudo permissions list for zimbra user (allows execution without password or with elevated privileges)
-
Verify binary ownership and permissionsRun: ls -la /opt/zimbra/bin/zmmailboxdmgrAffected if Binary is owned by root and has setuid bit, or is executable by zimbra user with elevated privileges
User is affected if Zimbra version is 9.0.0 or 10.0.0-10.0.6 AND the zmmailboxdmgr binary exists and is accessible to the zimbra user with elevated privileges.
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.7
Apply vendor patches for CVE-2024-27442 when released; until then, restrict sudo permissions on zmmailboxdmgr, monitor for suspicious command execution, and limit zimbra user access to only trusted personnel.
10.0.7
- Upgrade Zimbra Collaboration Server from version 10.0.0-10.0.6 to version 10.0.7 or later
- For version 9.0.0, contact Zimbra support for a patch or consider upgrading to the 10.0.7 release line
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-27442 — 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-27442 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