# CVE-2022-30333: RARLAB UnRAR Directory Traversal

> Attackers can exploit directory traversal in UnRAR to write arbitrary files, such as SSH keys, enabling remote code execution or privilege escalation.

- **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 9 Aug 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2022
- **Updated:** 1 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-30333, DLA-3534-1, GHSA-h4mr-p94x-gf79, MGASA-2022-0206, SUSE-SU-2022:1760-1, UBUNTU-CVE-2022-30333

## What is CVE-2022-30333?

CVE-2022-30333 is a critical path traversal vulnerability in Debian Debian Linux, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `unrar` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 5.6.1-4.8.1 |
| `unrar` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 5.6.1-4.8.1 |
| `unrar` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 5.6.1-4.8.1 |

Products: Debian Debian Linux, Rarlab Unrar.

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

Upgrade to a fixed version. US federal agencies must fix it by 30 Aug 2022.

## Is CVE-2022-30333 being exploited?

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

Public exploit code:

- https://github.com/rbowes-r7/unrar-cve-2022-30333-poc (github_poc): https://github.com/rbowes-r7/unrar-cve-2022-30333-poc
- https://github.com/TheL1ghtVn/CVE-2022-30333-PoC (github_poc): https://github.com/TheL1ghtVn/CVE-2022-30333-PoC
- Zimbra unrar vulnerability. Now there are already POC available, it is safe to release our POC. (github_poc): https://github.com/aslitsecurity/Zimbra-CVE-2022-30333
- UnRAR Path Traversal (CVE-2022-30333) (metasploit)
- UnRAR Path Traversal in Zimbra (CVE-2022-30333) (metasploit)
- https://github.com/RakhithJK/CVE-2022-30333 (github_poc): https://github.com/RakhithJK/CVE-2022-30333

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30333 is a critical path traversal vulnerability in Debian Debian Linux, published on 9 May 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-30333 in the wild since at least 9 Aug 2022, including in ransomware campaigns.

Affected product: Debian Debian Linux. 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-30333/ (Markdown: https://insights.sbomify.com/CVE-2022-30333/index.md)
```

## Sources

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

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