# CVE-2019-12170: File upload in n/a

> An attacker with an instructor account can upload a malicious ZIP archive to execute arbitrary code on the server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5vj3-gfgg-q9v5

## What is CVE-2019-12170?

CVE-2019-12170 is a high-severity vulnerability in n/a, published on 17 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ATutor through 2.2.4 is vulnerable to arbitrary file uploads via the mods/_core/backups/upload.php (aka backup) component. This may result in remote command execution. An attacker can use the instructor account to fully compromise the system using a crafted backup ZIP archive. This will allow for PHP files to be written to the web root, and for code to execute on the remote server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Atutor Atutor.

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

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

## Is CVE-2019-12170 being exploited?

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

Public exploit code:

- ATutor 2.2.4 'Backup' Remote Command Execution (CVE-2019-12170) (github_poc): https://github.com/fuzzlove/ATutor-Instructor-Backup-Arbitrary-File

## Other vulnerabilities in n/a

- [CVE-2014-9753](https://insights.sbomify.com/CVE-2014-9753/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-16114](https://insights.sbomify.com/CVE-2019-16114/): Missing authorization in n/a (critical 9.8)
- [CVE-2017-1000002](https://insights.sbomify.com/CVE-2017-1000002/): Path traversal in n/a (critical 9.8)
- [CVE-2017-1000003](https://insights.sbomify.com/CVE-2017-1000003/): Privilege escalation in n/a (critical 9.8)
- [CVE-2017-1000004](https://insights.sbomify.com/CVE-2017-1000004/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12170 is a high-severity vulnerability in n/a, published on 17 May 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-12170 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-12170/ (Markdown: https://insights.sbomify.com/CVE-2019-12170/index.md)
```

## Sources

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

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