# CVE-2017-8024: Cross-site scripting in EMC Isilon OneFS EMC Isilon OneFS versions prior to 8.1.0.1, EMC Isilon OneFS versions prior to 8.0.1.2, EMC Isilon OneFS versions prior to 8.0.0.6, EMC Isilon OneFS 7.2.1.x

> Reflected cross-site scripting in EMC Isilon OneFS allows malicious users to compromise the system via crafted requests.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-78v2-mphx-mx46

## What is CVE-2017-8024?

CVE-2017-8024 is a medium-severity cross-site scripting vulnerability in EMC Isilon OneFS EMC Isilon OneFS versions prior to 8.1.0.1, EMC Isilon OneFS versions prior to 8.0.1.2, EMC Isilon OneFS versions prior to 8.0.0.6, EMC Isilon OneFS 7.2.1.x, published on 18 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

EMC Isilon OneFS (versions prior to 8.1.0.1, versions prior to 8.0.1.2, versions prior to 8.0.0.6, version 7.2.1.x) is impacted by a reflected cross-site scripting vulnerability that may potentially be exploited by malicious users to compromise the affected system.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Emc Isilon Onefs.

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

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

## Is CVE-2017-8024 being exploited?

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

## Other vulnerabilities in EMC Isilon OneFS EMC Isilon OneFS versions prior to 8.1.0.1, EMC Isilon OneFS versions prior to 8.0.1.2, EMC Isilon OneFS versions prior to 8.0.0.6, EMC Isilon OneFS 7.2.1.x

- [CVE-2015-4525](https://insights.sbomify.com/CVE-2015-4525/): Command injection in n/a (critical 9.0)
- [CVE-2015-6848](https://insights.sbomify.com/CVE-2015-6848/): Privilege escalation in n/a (high 8.5)
- [CVE-2015-4545](https://insights.sbomify.com/CVE-2015-4545/): Auth bypass in n/a (high 8.0)
- [CVE-2018-11071](https://insights.sbomify.com/CVE-2018-11071/): DSA-2018-147: Dell EMC Isilon OneFS and IsilonSD Edge Remote Process Crash Vulnerability (high 7.5)
- [CVE-2017-4980](https://insights.sbomify.com/CVE-2017-4980/): Path traversal in EMC Isilon OneFS EMC Isilon OneFS 8.0.0 8.0.0.1, EMC Isilon OneFS 7.2.0 - 7.2.1.3, EMC Isilon OneFS 7.1.0 - 7.1.1.10 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8024 is a medium-severity cross-site scripting vulnerability in EMC Isilon OneFS EMC Isilon OneFS versions prior to 8.1.0.1, EMC Isilon OneFS versions prior to 8.0.1.2, EMC Isilon OneFS versions prior to 8.0.0.6, EMC Isilon OneFS 7.2.1.x, published on 18 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8024 in the wild and no public exploit code.

Affected product: EMC Isilon OneFS EMC Isilon OneFS versions prior to 8.1.0.1, EMC Isilon OneFS versions prior to 8.0.1.2, EMC Isilon OneFS versions prior to 8.0.0.6, EMC Isilon OneFS 7.2.1.x. 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-8024/ (Markdown: https://insights.sbomify.com/CVE-2017-8024/index.md)
```

## Sources

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

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