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

> Attackers can access files outside the intended directory via symbolic links, potentially reading or modifying sensitive data.

- **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:** No
- **Published:** 10 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-27gf-j34q-jwv5, openSUSE-SU-2024:12898-1

## What is CVE-2022-42725?

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

### Official description

Warpinator through 1.2.14 allows access outside of an intended directory, as demonstrated by symbolic directory links.

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

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

It affects 1 product.


Products: Linuxmint Warpinator.

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

No fix has been published for CVE-2022-42725 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-42725 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29380](https://insights.sbomify.com/CVE-2023-29380/): Warpinator before 1.6.0 allows remote file deletion via directory traversal in top_dir_basenames. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42725 is a high-severity path traversal vulnerability in n/a, published on 10 Oct 2022. 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-42725 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-42725/ (Markdown: https://insights.sbomify.com/CVE-2022-42725/index.md)
```

## Sources

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

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