# CVE-2022-22701: Path traversal in PartKeepr

> An authenticated user can read local files by exploiting the file:// URI scheme in attachment loading.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4vq7-xgx9-437g

## What is CVE-2022-22701?

CVE-2022-22701 is a medium-severity path traversal vulnerability in PartKeepr, published on 7 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PartKeepr versions up to v1.4.0, loads attachments using a URL while creating a part and allows the use of the 'file://' URI scheme, allowing an authenticated user to read local files.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Partkeepr Partkeepr.

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

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

## Is CVE-2022-22701 being exploited?

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

## Other vulnerabilities in PartKeepr

- [CVE-2021-39390](https://insights.sbomify.com/CVE-2021-39390/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-30899](https://insights.sbomify.com/CVE-2022-30899/): Cross-site scripting in n/a (medium 4.8)
- [CVE-2022-22702](https://insights.sbomify.com/CVE-2022-22702/): Server-side request forgery in PartKeepr (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22701 is a medium-severity path traversal vulnerability in PartKeepr, published on 7 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22701 in the wild and no public exploit code.

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

## Sources

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

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