# CVE-2019-12902: Information disclosure in n/a

> Incomplete data cleanup allows new users with reused IDs to access deleted users' data in Pydio Cells.

- **Severity:** Medium 6.5 (`CVSS:3.0/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:** 19 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-33h5-8f42-7frx

## What is CVE-2019-12902?

CVE-2019-12902 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pydio Cells before 1.5.0 does incomplete cleanup of a user's data upon deletion. This allows a new user, holding the same User ID as a deleted user, to restore the deleted user's data.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2019-12902?

It affects 1 product.


Products: Pydio Cells.

## How do I fix CVE-2019-12902?

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

## Is CVE-2019-12902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-32749](https://insights.sbomify.com/CVE-2023-32749/): Privilege escalation in n/a (high 8.8)
- [CVE-2019-12901](https://insights.sbomify.com/CVE-2019-12901/): Path traversal in n/a (high 8.8)
- [CVE-2020-12851](https://insights.sbomify.com/CVE-2020-12851/): Path traversal in n/a (high 8.1)
- [CVE-2020-12847](https://insights.sbomify.com/CVE-2020-12847/): Command injection in n/a (high 7.2)
- [CVE-2020-12850](https://insights.sbomify.com/CVE-2020-12850/): The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4. (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12902 and fix it if it is affected.

What it is: CVE-2019-12902 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12902 in the wild and no public exploit code.

Affected product: n/a. 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-2019-12902/ (Markdown: https://insights.sbomify.com/CVE-2019-12902/index.md)
```

## Sources

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

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