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

> Remote attackers can upload and execute arbitrary files via the ConnectionId parameter in ManageEngine Desktop Central.

- **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:** 27 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c9wc-3x6x-mqrc

## What is CVE-2015-8249?

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

### Official description

The FileUploadServlet class in ManageEngine Desktop Central 9 before build 91093 allows remote attackers to upload and execute arbitrary files via the ConnectionId parameter.

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

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

It affects 1 product.


Products: Manageengine Desktop Central.

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

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

## Is CVE-2015-8249 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8249 exists.

Public exploit code:

- ManageEngine Desktop Central 9 FileUploadServlet ConnectionId Vulnerability (metasploit)
- ManageEngine Desktop Central 9 - FileUploadServlet ConnectionId (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-28960](https://insights.sbomify.com/CVE-2021-28960/): Command injection in n/a (critical 9.8)
- [CVE-2014-3996](https://insights.sbomify.com/CVE-2014-3996/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8249 is a critical vulnerability in n/a, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8249 exists.

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-8249/ (Markdown: https://insights.sbomify.com/CVE-2015-8249/index.md)
```

## Sources

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

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