dbcve.org
Isilon OnefsOperating system · Emc

CVE-2017-14387

MEDIUM · 6.5 CVSS v3.0 Published 2017-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The NFS service in EMC Isilon OneFS fails to properly propagate default security flavor changes to NFS exports configured to use default settings. When an administrator changes the default security flavor, exports mounted after this change may still use the original (potentially weaker) default authentication method rather than the newly configured one, allowing clients to access exports with weaker security than intended.

MitigationReview all NFS exports configured to use default settings and explicitly configure the desired security flavor on each export. Verify that mounted exports are using the intended authentication method rather than the fallback default.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Isilon OnefsOperating system
Affected:= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.1.0= 8.0.1.1= 8.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Isilon OneFS version
    Run 'isi version' or check the OneFS web UI under Cluster Management > Overview to find the installed OneFS version
    Affected if The installed version matches any of these: 8.0.0.0, 8.0.0.1, 8.0.0.2, 8.0.0.3, 8.0.0.4, 8.1.0.0, 8.1.1.0
  2. Identify NFS exports using default security settings
    Run 'isi nfs exports list' or view exports via OneFS web UI under Protocol Configuration > NFS > Exports. Look for exports where the security flavor is set to 'default' or not explicitly configured
    Affected if There are NFS exports configured to use default security settings rather than an explicit security flavor
  3. Check the current default security flavor configuration
    Run 'isi nfs settings global view' or check Protocol Configuration > NFS > Settings in the web UI to see the current default security flavor setting
    Affected if A default security flavor is configured (this sets the baseline for what should be used)
  4. Verify actual security flavor used by mounted exports
    Run 'isi nfs exports list -v' to show detailed export info, then check with 'showmount -e <export>' from a client or review access logs to see which security flavor clients are actually using for authentication
    Affected if Mounted exports are using a different (weaker) security flavor than the current default configuration, indicating they retained an older default

You are affected if your OneFS version is 8.0.0.0 through 8.1.1.0 AND you have NFS exports using default security settings where mounted exports are authenticating with a weaker security flavor than your current default configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review all NFS exports configured to use default settings and explicitly configure the desired security flavor on each export. Verify that mounted exports are using the intended authentication method rather than the fallback default.

Fix this in Isilon Onefs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14387 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data