# CVE-2020-12850: The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4.


- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7hh6-jvfj-8w78

## What is CVE-2020-12850?

CVE-2020-12850 is a high-severity vulnerability in n/a, published on 11 Jun 2020. 

### Official description

The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4. Prior versions of the Pydio Cells Enterprise OVF (such as version 2.0.3) have a looser policy restriction allowing the “pydio” user to execute any privileged command using sudo. In version 2.0.4 of the appliance, the user pydio is responsible for running all the services and binaries that are contained in the Pydio Cells web application package, such as mysqld, cells, among others. This user has privileges restricted to run those services and nothing more.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-12850?

It affects 1 product.


Products: Pydio Cells.

## How do I fix CVE-2020-12850?

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

## Is CVE-2020-12850 being exploited?

There is no known exploitation of CVE-2020-12850 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-12852](https://insights.sbomify.com/CVE-2020-12852/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12850 and fix it if it is affected.

What it is: CVE-2020-12850 is a high-severity vulnerability in n/a, published on 11 Jun 2020. 
Exploitation: There is no known exploitation of CVE-2020-12850 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-2020-12850/ (Markdown: https://insights.sbomify.com/CVE-2020-12850/index.md)
```

## Sources

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

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