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

> An authenticated user can upload a malicious script to the Personal Library, leading to arbitrary code execution within the application context.

- **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:** 13 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-96x4-p3v5-f78p

## What is CVE-2017-16251?

CVE-2017-16251 is a high-severity vulnerability in n/a, published on 13 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the conferencing component of Mitel ST 14.2, release GA28 and earlier, could allow an authenticated user to upload a malicious script to the Personal Library by a crafted POST request. Successful exploit could allow an attacker to execute arbitrary code within the context of the application.

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

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

It affects 1 product.


Products: Mitel St14.2.

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

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

## Is CVE-2017-16251 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16250](https://insights.sbomify.com/CVE-2017-16250/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16251 is a high-severity vulnerability in n/a, published on 13 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16251 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-16251/ (Markdown: https://insights.sbomify.com/CVE-2017-16251/index.md)
```

## Sources

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

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