# CVE-2014-5302: Path traversal in n/a

> Authenticated attackers can exploit a directory traversal flaw in ManageEngine IT management products 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:** 28 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3qx5-mr88-qhv7

## What is CVE-2014-5302?

CVE-2014-5302 is a high-severity path traversal vulnerability in n/a, published on 28 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in ServiceDesk Plus and Plus MSP v5 through v9.0 v9030; AssetExplorer v4 to v6.1; SupportCenter v5 to v7.9; IT360 v8 to v10.4 allows remote authenticated users to execute arbitrary code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-5302?

It affects 4 products.


Products: Manageengine Assetexplorer, Manageengine It360, Manageengine Servicedesk Plus, Manageengine Supportcenter.

## How do I fix CVE-2014-5302?

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

## Is CVE-2014-5302 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5301](https://insights.sbomify.com/CVE-2014-5301/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5302 and fix it if it is affected.

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

## Sources

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

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