# CVE-2017-14387: Security feature bypass in EMC Isilon OneFS EMC Isilon OneFS 8.1.0.0, EMC Isilon OneFS 8.0.1.0 -- 8.0.1.1, EMC Isilon OneFS 8.0.0.0 8.0.0.4

> NFS clients may access exports using weaker default security settings despite administrator configuration, bypassing intended authentication controls.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 20 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c7vw-9fhg-crj3

## What is CVE-2017-14387?

CVE-2017-14387 is a medium-severity vulnerability in EMC Isilon OneFS EMC Isilon OneFS 8.1.0.0, EMC Isilon OneFS 8.0.1.0 -- 8.0.1.1, EMC Isilon OneFS 8.0.0.0 8.0.0.4, published on 20 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NFS service in EMC Isilon OneFS 8.1.0.0, 8.0.1.0 - 8.0.1.1, and 8.0.0.0 - 8.0.0.4 maintains default NFS export settings (including the NFS export security flavor for authentication) that can be leveraged by current and future NFS exports. This NFS service contained a flaw that did not properly propagate changes made to the default security flavor to all new and existing NFS exports that are configured to use default NFS export settings and that are mounted after those changes are made. This flaw may potentially allow NFS clients to access affected NFS exports using the default and potentially weaker security flavor even if a more secure one was selected to be used by the OneFS administrator, aka an "NFS Export Security Setting Fallback Vulnerability."

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

It affects 1 product.


Products: Emc Isilon Onefs.

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

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

## Is CVE-2017-14387 being exploited?

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

## Other vulnerabilities in EMC Isilon OneFS EMC Isilon OneFS 8.1.0.0, EMC Isilon OneFS 8.0.1.0 -- 8.0.1.1, EMC Isilon OneFS 8.0.0.0 8.0.0.4

- [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-14387 and fix it if it is affected.

What it is: CVE-2017-14387 is a medium-severity vulnerability in EMC Isilon OneFS EMC Isilon OneFS 8.1.0.0, EMC Isilon OneFS 8.0.1.0 -- 8.0.1.1, EMC Isilon OneFS 8.0.0.0 8.0.0.4, published on 20 Dec 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-14387 in the wild and no public exploit code.

Affected product: EMC Isilon OneFS EMC Isilon OneFS 8.1.0.0, EMC Isilon OneFS 8.0.1.0 -- 8.0.1.1, EMC Isilon OneFS 8.0.0.0 8.0.0.4. 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-14387/ (Markdown: https://insights.sbomify.com/CVE-2017-14387/index.md)
```

## Sources

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

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