CVE-2017-4987
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 VNX2 versions prior to OE for File 8.1.9.211 and VNX1 versions prior to OE for File 7.1.80.8, a local authenticated user can load a maliciously crafted file in the search path which may potentially allow the attacker to execute arbitrary code on the targeted VNX Control Station system, aka an uncontrolled search path 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 · high confidenceEMC VNX2 and VNX1 Control Stations contain an uncontrolled search path vulnerability where a local authenticated user can place a maliciously crafted DLL or executable in the application's search path, causing it to be loaded and executed with elevated privileges, allowing arbitrary code execution on the targeted system.
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 dataall versionsall versionsCVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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 device modelAccess the Control Station management interface or CLI and verify the system is an EMC VNX1 or VNX2 storage system. This is typically visible in the system overview or via the 'naviseccli' command: naviseccli -getagentAffected if The system is a VNX1 or VNX2 Control Station
-
Check VNX2 firmware versionOn the VNX2 Control Station, run 'firmware -list' or access the Unisphere interface to view the OE for File firmware version. Look for a version number such as 8.1.xAffected if The VNX2 firmware version is any version (all versions are affected)
-
Check VNX1 firmware versionOn the VNX1 Control Station, run 'firmware -list' or access the Unisphere interface to view the OE for File firmware version. Look for a version number such as 7.1.xAffected if The VNX1 firmware version is any version (all versions are affected)
-
Confirm Control Station component is presentVerify the system has an active Control Station component by checking the storage system configuration via naviseccli or the Unisphere management console. The vulnerability exists in the Control Station specifically.Affected if The Control Station component is present and running on a VNX1 or VNX2 system
The environment is affected if the system is an EMC VNX1 or VNX2 Control Station running any firmware version, since all versions of both products are vulnerable to DLL preloading attacks.
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 dataApply the vendor patch by upgrading VNX2 to OE for File 8.1.9.211 or later, and VNX1 to OE for File 7.1.80.8 or later. Coordinate a planned maintenance window with thorough pre-update backups and post-update verification.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4987 — 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-4987 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