# CVE-2022-39210: Access to internal files of the Nextcloud Android app

> Attackers can access internal files of the Nextcloud Android app, potentially leaking sensitive information.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-nextcloud-2022-39210, GHSA-vw2w-gpcv-v39f

## What is CVE-2022-39210?

CVE-2022-39210 is a low-severity path traversal vulnerability in nextcloud security-advisories, published on 16 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Nextcloud android is the official Android client for the Nextcloud home server platform. Internal paths to the Nextcloud Android app files are not properly protected. As a result access to internal files of the from within the Nextcloud Android app is possible. This may lead to a leak of sensitive information in some cases. It is recommended that the Nextcloud Android app is upgraded to 3.21.0. There are no known workarounds for this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

1 open source package ship an affected version, including nextcloud. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nextcloud` | Bitnami | All versions | 3.21.0 |

Products: Nextcloud Nextcloud.

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

Upgrade nextcloud to 3.21.0 or later.

## Is CVE-2022-39210 being exploited?

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

## Other vulnerabilities in nextcloud security-advisories

- [CVE-2019-5454](https://insights.sbomify.com/CVE-2019-5454/): SQL injection in com.nextcloud.client (critical 9.8)
- [CVE-2021-43863](https://insights.sbomify.com/CVE-2021-43863/): SQL Injection in FileContentProvider (GHSL-2021-1007) (high 7.5)
- [CVE-2019-5450](https://insights.sbomify.com/CVE-2019-5450/): Cross-site scripting in com.nextcloud.client (medium 6.8)
- [CVE-2019-5455](https://insights.sbomify.com/CVE-2019-5455/): Auth bypass in com.nextcloud.client (medium 6.8)
- [CVE-2021-22905](https://insights.sbomify.com/CVE-2021-22905/): Information disclosure in Nextcloud Android App (com.nextcloud.client) (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39210 is a low-severity path traversal vulnerability in nextcloud security-advisories, published on 16 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-39210 in the wild and no public exploit code.

Affected packages and fixed versions:
- nextcloud (Bitnami): affected all versions; fixed in 3.21.0

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

## Sources

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

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