# CVE-2022-37042: Synacor Zimbra Collaboration Suite (ZCS) Authentication Bypass

> Attackers can bypass authentication to upload arbitrary files via mboximport, leading to directory traversal and remote code execution.

- **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 11 Aug 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2022
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-9g5r-3vrr-xfcm

## What is CVE-2022-37042?

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

### Official description

Zimbra Collaboration Suite (ZCS) 8.8.15 and 9.0 has mboximport functionality that receives a ZIP archive and extracts files from it. By bypassing authentication (i.e., not having an authtoken), an attacker can upload arbitrary files to the system, leading to directory traversal and remote code execution. NOTE: this issue exists because of an incomplete fix for CVE-2022-27925.

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

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

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

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

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

## Is CVE-2022-37042 being exploited?

Yes. Attackers have exploited CVE-2022-37042 in the wild since at least 11 Aug 2022, including in ransomware campaigns.

Public exploit code:

- CVE-2022-37042 Zimbra Auth Bypass leads to RCE (github_poc): https://github.com/0xf4n9x/CVE-2022-37042
- Zimbra CVE-2022-37042 Nuclei weaponized template (github_poc): https://github.com/aels/CVE-2022-37042
- https://github.com/GreyNoise-Intelligence/Zimbra_CVE-2022-37042-_CVE-2022-27925 (github_poc): https://github.com/GreyNoise-Intelligence/Zimbra_CVE-2022-37042-_CVE-2022-27925
- Zip Path Traversal in Zimbra (mboximport) (CVE-2022-27925) (metasploit)
- Zimbra Collaboration Suite 8.8.15/9.0 - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-37042.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-41352](https://insights.sbomify.com/CVE-2022-41352/): Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload (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-37042 and fix it if it is affected.

What it is: CVE-2022-37042 is a critical path traversal vulnerability in Synacor Zimbra Collaboration Suite, published on 11 Aug 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-37042 in the wild since at least 11 Aug 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-37042/ (Markdown: https://insights.sbomify.com/CVE-2022-37042/index.md)
```

## Sources

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

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