SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2022-41352Public Intelligence Dossier
Source: synacor · Limited verification•Last verified: •Collection Degraded
CVE-2022-41352ListedCRITICAL (raw)CVSS 9.8CWE-22

An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15 and 9.0

Published: 26 Sept 2022•Last updated: 10 Sept 2026, 09:47 AM IST•Source identifier: cve@mitre.org
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added20 Oct 2022
Due10 Nov 2022
RansomwareKnown
CVSS score
9.8CRITICAL (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Metric sourcenvd@nist.gov
EPSS probability
95.5%0.955
Percentile100th
Weakness type
CWE-22
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15 and 9.0. An attacker can upload arbitrary files through amavis via a cpio loophole (extraction to /opt/zimbra/jetty/webapps/zimbra/public) that can lead to incorrect access to any other user accounts. Zimbra recommends pax over cpio. Also, pax is in the prerequisites of Zimbra on Ubuntu; however, pax is no longer part of a default Red Hat installation after RHEL 6 (or CentOS 6). Once pax is installed, amavis automatically prefers it over cpio.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; CRITICAL severity; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • synacor zimbra collaboration suite · 9.0.0; 8.8.15 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply updates per vendor instructions.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply updates per vendor instructions.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); path-traversal (CWE-22)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Locate affected deployments and the path-handling endpoint named by the advisory.Telemetry: Application access logs · The affected path must come from the source, not the CWE alone. · Rule path-traversal

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review requests to that endpoint for traversal encodings and unusual file responses.Telemetry: Application access logs · Such patterns are a hypothesis to validate against normal traffic. · Rule path-traversal

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
20 Oct 2022
Required action due
10 Nov 2022
Known ransomware use
Known

Apply updates per vendor instructions.

Change History & Source Data

— No recorded material change

CNA / source
cve@mitre.org
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:-:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p1:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p10:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p11:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p12:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p13:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p14:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p15:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p16:*:*:*:*:*:*, cpe:2.3:a:synacor:zimbra_collaboration_suite:9.0.0:p17:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2022-10-20forums.zimbra.orgSource recordnvd.nist.govSource recordwiki.zimbra.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2022-41352
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2022-41352
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2022-41352"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.