CVE-2017-14380
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 · uneditedIn EMC Isilon OneFS 8.1.0.0, 8.0.1.0 - 8.0.1.1, 8.0.0.0 - 8.0.0.4, 7.2.1.0 - 7.2.1.5, 7.2.0.x, and 7.1.1.x, a malicious compliance admin (compadmin) account user could exploit a vulnerability in isi_get_itrace or isi_get_profile maintenance scripts to run any shell script as system root on a cluster in compliance mode. This could potentially lead to an elevation of privilege for the compadmin user and violate compliance mode.
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 · high confidenceA malicious compliance admin (compadmin) user can exploit a vulnerability in the isi_get_itrace or isi_get_profile maintenance scripts to execute arbitrary shell scripts as root, enabling privilege escalation on Isilon OneFS clusters running in compliance mode.
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= 7.1.1.0= 7.1.1.1= 7.1.1.2= 7.1.1.3= 7.1.1.4= 7.1.1.5= 7.2.0.0= 7.2.0.1= 7.2.0.2= 7.2.0.3= 7.2.0.4= 7.2.0.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the OneFS versionRun 'isi version' or check the cluster management UI for the OneFS version numberAffected if The installed version matches any of these: 7.1.1.0, 7.1.1.1, 7.1.1.2, 7.1.1.3, 7.1.1.4, 7.1.1.5, 7.2.0.0, 7.2.0.1, 7.2.0.2, 7.2.0.3, 7.2.0.4, 7.2.0.5
-
Determine if the cluster is in compliance modeRun 'isi_gather_info --comply' or check the security settings in the OneFS web UI for compliance mode statusAffected if The cluster is running in compliance mode (compliance mode is enabled)
-
Check for compadmin user presenceRun 'isi auth users view compadmin' or list users in the 'Compliance Administrators' group using 'isi auth groups view 'Compliance Administrators''Affected if A compadmin (compliance admin) account exists on the system
-
Locate the maintenance scriptsCheck for the presence of isi_get_itrace and isi_get_profile in /usr/local/bin or similar paths using 'find /usr -name isi_get_itrace' and 'find /usr -name isi_get_profile'Affected if The scripts isi_get_itrace or isi_get_profile exist on the system and are executable by compadmin users
-
Review audit logs for script executionSearch compliance audit logs or system logs for recent executions of isi_get_itrace or isi_get_profile using grep or the OneFS log viewer, looking for unusual or unauthorized invocationsAffected if There are log entries showing execution of these maintenance scripts by non-root users or at unexpected times
The environment is affected if the OneFS version matches any of the affected versions listed AND the cluster is running in compliance mode with a compadmin account present.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of OneFS that addresses this vulnerability, and review compliance admin access controls and audit logging on affected systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14380 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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