# CVE-2017-7258: Path traversal in n/a

> Attackers can exploit directory path traversal to view restricted information or execute commands on the web server, leading to full system compromise.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ff76-qqwc-mj6r

## What is CVE-2017-7258?

CVE-2017-7258 is a high-severity path traversal vulnerability in n/a, published on 29 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP Exploit in eMLi Portal in AuroMeera Technometrix Pvt. Ltd. eMLi allows an Attacker to View Restricted Information or (even more seriously) execute powerful commands on the web server which can lead to a full compromise of the system via Directory Path Traversal, as demonstrated by reading core-emli/Storage. The affected versions are eMLi School Management 1.0, eMLi College Campus Management 1.0, and eMLi University Management 1.0.

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

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

It affects 1 product.


Products: Auromeera Emli.

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

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

## Is CVE-2017-7258 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7621](https://insights.sbomify.com/CVE-2017-7621/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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