# CVE-2019-9642: Code injection in n/a

> Unauthenticated attackers can execute arbitrary PHP code by uploading a malicious file and accessing it via the proxy endpoint.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwvv-q6jf-62c9, UBUNTU-CVE-2019-9642

## What is CVE-2019-9642?

CVE-2019-9642 is a critical code injection vulnerability in n/a, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in proxy.php in pydio-core in Pydio through 8.2.2. Through an unauthenticated request, it possible to evaluate malicious PHP code by placing it on the fourth line of a .php file, as demonstrated by a PoC.php created by the guest account, with execution via a proxy.php?hash=../../../../../var/lib/pydio/data/personal/guest/PoC.php request. This is related to plugins/action.share/src/Store/ShareStore.php.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Pydio Pydio.

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

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

## Is CVE-2019-9642 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4267](https://insights.sbomify.com/CVE-2013-4267/): Command injection in Ajaxeplorer (critical 9.8)
- [CVE-2018-20718](https://insights.sbomify.com/CVE-2018-20718/): Deserialization in n/a (critical 9.8)
- [CVE-2015-3431](https://insights.sbomify.com/CVE-2015-3431/): Command injection in n/a (critical 9.8)
- [CVE-2019-20452](https://insights.sbomify.com/CVE-2019-20452/): Deserialization in n/a (high 8.8)
- [CVE-2019-20453](https://insights.sbomify.com/CVE-2019-20453/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9642 is a critical code injection vulnerability in n/a, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9642 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-9642/ (Markdown: https://insights.sbomify.com/CVE-2019-9642/index.md)
```

## Sources

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

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