# CVE-2022-41352: Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload

> Attackers can upload arbitrary files via a cpio loophole in Zimbra, potentially accessing other user accounts unless pax is installed.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 Oct 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2022
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-85q4-vgvj-3q28

## What is CVE-2022-41352?

CVE-2022-41352 is a critical path traversal vulnerability in Synacor Zimbra Collaboration Suite, published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-41352?

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

## How do I fix CVE-2022-41352?

No fix has been published for CVE-2022-41352 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Nov 2022.

## Is CVE-2022-41352 being exploited?

Yes. Attackers have exploited CVE-2022-41352 in the wild since at least 20 Oct 2022, including in ransomware campaigns.

Public exploit code:

- Zimbra <9.0.0.p27 RCE (github_poc): https://github.com/Cr4ckC4t/cve-2022-41352-zimbra-rce
- cve-2022-41352 poc (github_poc): https://github.com/segfault-it/cve-2022-41352
- TAR Path Traversal in Zimbra (CVE-2022-41352) (metasploit)
- https://github.com/dafrax/cve-2022-41352-zimbra-rce (github_poc): https://github.com/dafrax/cve-2022-41352-zimbra-rce
- Zimbra Collaboration - Unrestricted File Upload (nuclei): http/cves/2022/CVE-2022-41352.yaml

## Other vulnerabilities in Synacor Zimbra Collaboration Suite

- [CVE-2024-45519](https://insights.sbomify.com/CVE-2024-45519/): Synacor Zimbra Collaboration Suite (ZCS) Command Execution (critical 10.0, exploited in the wild)
- [CVE-2022-37042](https://insights.sbomify.com/CVE-2022-37042/): Synacor Zimbra Collaboration Suite (ZCS) Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-27924](https://insights.sbomify.com/CVE-2022-27924/): Synacor Zimbra Collaboration Suite (ZCS) Command Injection (critical 9.8, exploited in the wild)
- [CVE-2020-7796](https://insights.sbomify.com/CVE-2020-7796/): Synacor Zimbra Collaboration Suite (ZCS) Server-Side Request Forgery (critical 9.8, exploited in the wild)
- [CVE-2019-9670](https://insights.sbomify.com/CVE-2019-9670/): Synacor Zimbra Collaboration Suite (ZCS) Improper Restriction of XML External Entity Reference (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41352 and fix it if it is affected.

What it is: CVE-2022-41352 is a critical path traversal vulnerability in Synacor Zimbra Collaboration Suite, published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-41352 in the wild since at least 20 Oct 2022, including in ransomware campaigns.

Affected product: Synacor Zimbra Collaboration Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41352/ (Markdown: https://insights.sbomify.com/CVE-2022-41352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41352
- OSV: https://osv.dev/vulnerability/CVE-2022-41352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41352/
Summaries are generated and may contain mistakes; the official description above is the record.