# CVE-2015-5601: File upload in n/a

> Privileged users can execute arbitrary code via mishandled tar.gz files in the course import endpoint of the edX platform.

- **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:** 29 Jul 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x9r5-6wwv-rqw2

## What is CVE-2015-5601?

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

### Official description

edx-platform before 2015-07-20 allows code execution by privileged users because the course import endpoint mishandles .tar.gz files.

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

## Which versions are affected by CVE-2015-5601?

It affects 1 product.


Products: Edx Edx-Platform.

## How do I fix CVE-2015-5601?

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

## Is CVE-2015-5601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10766](https://insights.sbomify.com/CVE-2016-10766/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-18380](https://insights.sbomify.com/CVE-2017-18380/): Open redirect in n/a (high 7.5)
- [CVE-2017-18381](https://insights.sbomify.com/CVE-2017-18381/): Hardcoded credentials in n/a (high 7.2)
- [CVE-2024-22209](https://insights.sbomify.com/CVE-2024-22209/): XBlock custom auth does not respect JWT Scopes (medium 6.4)
- [CVE-2021-39248](https://insights.sbomify.com/CVE-2021-39248/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5601 and fix it if it is affected.

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

## Sources

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

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