# CVE-2022-48579: Path traversal in n/a

> Attackers can extract files outside the destination folder via symlink chains, potentially reading or modifying arbitrary files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** AZL-27870, AZL-34592, CLEANSTART-2026-QU46977, DEBIAN-CVE-2022-48579, DLA-3535-1, GHSA-pg3x-qpq9-p4v6, UBUNTU-CVE-2022-48579

## What is CVE-2022-48579?

CVE-2022-48579 is a high-severity path traversal vulnerability in n/a, published on 7 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UnRAR before 6.2.3 allows extraction of files outside of the destination folder via symlink chains.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Rarlab Unrar.

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

Upgrade to a fixed version.

## Is CVE-2022-48579 being exploited?

There is no known exploitation of CVE-2022-48579 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-12940](https://insights.sbomify.com/CVE-2017-12940/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12941](https://insights.sbomify.com/CVE-2017-12941/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12942](https://insights.sbomify.com/CVE-2017-12942/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-6706](https://insights.sbomify.com/CVE-2012-6706/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-20006](https://insights.sbomify.com/CVE-2017-20006/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48579 is a high-severity path traversal vulnerability in n/a, published on 7 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48579 in the wild and no public exploit code.

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

## Sources

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

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