# CVE-2022-29160: Sensitive files/data exist after deletion of user account in Nextcloud Android

> Sensitive tokens and user data remain accessible after account deletion in the Nextcloud Android app, potentially exposing private information.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2022
- **Updated:** 22 Apr 2025
- **Also known as:** BIT-nextcloud-2022-29160, GHSA-xcj9-3jch-qr2r

## What is CVE-2022-29160?

CVE-2022-29160 is a low-severity vulnerability in nextcloud security-advisories, published on 20 May 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 Android client for Nextcloud, a self-hosted productivity platform. Prior to version 3.19.0, sensitive tokens, images, and user related details exist after deletion of a user account. This could result in misuse of the former account holder's information. Nextcloud Android version 3.19.0 contains a patch for this issue. There are no known workarounds available.

Weakness: CWE-459 (Incomplete Cleanup), CWE-284 (Improper Access Control)

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

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


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

Products: Nextcloud Nextcloud.

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

Upgrade nextcloud to 3.19.0 or later.

## Is CVE-2022-29160 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29160 exists.

## 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-29160 and fix it if it is affected.

What it is: CVE-2022-29160 is a low-severity vulnerability in nextcloud security-advisories, published on 20 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29160 exists.

Affected packages and fixed versions:
- nextcloud (Bitnami): affected all versions; fixed in 3.19.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-29160/ (Markdown: https://insights.sbomify.com/CVE-2022-29160/index.md)
```

## Sources

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

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