# CVE-2017-15580: File upload in n/a

> Attackers can upload arbitrary malicious files due to insufficient content validation, potentially leading to remote code execution on the server.

- **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:** 23 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3grx-cccr-q3vw

## What is CVE-2017-15580?

CVE-2017-15580 is a critical vulnerability in n/a, published on 23 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

osTicket 1.10.1 provides a functionality to upload 'html' files with associated formats. However, it does not properly validate the uploaded file's contents and thus accepts any type of file, such as with a tickets.php request that is modified with a .html extension changed to a .exe extension. An attacker can leverage this vulnerability to upload arbitrary files on the web application having malicious content.

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

## Which versions are affected by CVE-2017-15580?

It affects 1 product.


Products: Osticket Osticket.

## How do I fix CVE-2017-15580?

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

## Is CVE-2017-15580 being exploited?

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

Public exploit code:

- osTicket 1.10.1 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-14396](https://insights.sbomify.com/CVE-2017-14396/): SQL injection in n/a (critical 9.8)
- [CVE-2005-1437](https://insights.sbomify.com/CVE-2005-1437/): SQL injection in n/a (high 7.5)
- [CVE-2005-1438](https://insights.sbomify.com/CVE-2005-1438/): Code injection in n/a (high 7.5)
- [CVE-2017-15362](https://insights.sbomify.com/CVE-2017-15362/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-45387](https://insights.sbomify.com/CVE-2025-45387/): Missing authorization in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15580 and fix it if it is affected.

What it is: CVE-2017-15580 is a critical vulnerability in n/a, published on 23 Oct 2017. 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-2017-15580 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-2017-15580/ (Markdown: https://insights.sbomify.com/CVE-2017-15580/index.md)
```

## Sources

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

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