# CVE-2022-4773: cloudsync LocalFilesystemConnector.java getItem path traversal

> A path traversal vulnerability in cloudsync allows local attackers to read or modify arbitrary files via the getItem function.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fcc5-xvq6-8cg4

## What is CVE-2022-4773?

CVE-2022-4773 is a low-severity path traversal vulnerability in cloudsync, published on 27 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as problematic was found in cloudsync. Affected by this vulnerability is the function getItem of the file src/main/java/cloudsync/connector/LocalFilesystemConnector.java. The manipulation leads to path traversal. It is possible to launch the attack on the local host. The name of the patch is 3ad796833398af257c28e0ebeade68518e0e612a. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216919. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

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

It affects 1 product.


Products: Cloudsync Project Cloudsync.

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

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

## Is CVE-2022-4773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4773 is a low-severity path traversal vulnerability in cloudsync, published on 27 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4773 in the wild and no public exploit code.

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

## Sources

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

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