# CVE-2022-27621: Path traversal in USB Copy

> Remote authenticated users can read or write arbitrary files via path traversal in Synology USB Copy webapi component.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5qww-32pm-m8vq

## What is CVE-2022-27621?

CVE-2022-27621 is a medium-severity path traversal vulnerability in Synology USB Copy, published on 3 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in webapi component in Synology USB Copy before 2.2.0-1086 allows remote authenticated users to read or write arbitrary files via unspecified vectors.

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

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

It affects 1 product.


Products: Synology Usb Copy.

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

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

## Is CVE-2022-27621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27621 is a medium-severity path traversal vulnerability in Synology USB Copy, published on 3 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27621 in the wild and no public exploit code.

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

## Sources

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

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