LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41347: An issue was discovered in Zimbra Collaboration (ZCS) 8.8.x and 9.x (e.g., 8.8.15).

An issue was discovered in Zimbra Collaboration (ZCS) 8.8.x and 9.x (e.g., 8.8.15). The Sudo configuration permits the zimbra user to execute the NGINX binary as root with arbitrary parameters. As part of its intended functionality, NGINX can load a user-defined configuration file, which includes plugins in the form of .so files, which also execute as root.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can turn limited access on a vulnerable Zimbra Collaboration server into full root control. It matters most after an attacker has already reached the zimbra user context. The source bundle does not show CISA KEV listing or confirmed active exploitation, but public exploit-focused references exist.

Executive priority

Treat this as a high-priority hardening and patch-validation item for Zimbra servers. It can convert a foothold into full server compromise, which is serious for email infrastructure, but the provided evidence does not support calling it actively exploited.

Technical view

ZCS 8.8.x and 9.x, including 8.8.15, allowed the zimbra user to run NGINX as root with arbitrary parameters through sudo. Because NGINX can load user-specified configuration and shared-object plugins, that path can execute code with root privileges. CVSS 3.1 is 7.8: local, low complexity, low privileges, no user interaction.

Likely exposure

Organizations running Zimbra Collaboration 8.8.x or 9.x are the relevant exposure group. Practical risk is highest where an attacker can obtain local access, shell access, or application-level execution as the zimbra user on the mail server.

Exploitation context

The bundle includes public exploit-oriented references, but does not include KEV status or a cited source confirming active exploitation. This is not described as a remote unauthenticated entry point; it is a local privilege-escalation path from zimbra-level access to root.

Researcher notes

The key exposure condition is access as the zimbra user. The supplied CVE text explains the root cause and privilege boundary failure, but the bundle does not provide a specific fixed version, patch date, or official mitigation text beyond Zimbra advisory locations.

Mitigation direction

  • Check Zimbra Security Advisories for the vendor-supported remediation for your exact ZCS version.
  • Upgrade or patch affected ZCS 8.8.x and 9.x systems according to Zimbra guidance.
  • Review sudo policy for zimbra-to-root NGINX execution with arbitrary parameters.
  • Limit shell and administrative access paths that can reach the zimbra user context.
  • Increase monitoring on Zimbra hosts until vendor remediation is confirmed.

Validation and detection

  • Inventory ZCS versions and flag 8.8.x and 9.x deployments.
  • Verify whether local sudo rules permit zimbra to run NGINX as root with arbitrary parameters.
  • Confirm remediation status against Zimbra Security Advisories and Security Center guidance.
  • Review host logs for unusual zimbra-initiated NGINX activity or unexpected root-level changes.
  • Check whether public-facing Zimbra systems have any prior compromise indicators.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-41347 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-41347Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.