CVE-2017-14375
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 · uneditedEMC Unisphere for VMAX Virtual Appliance (vApp) versions prior to 8.4.0.15, EMC Solutions Enabler Virtual Appliance versions prior to 8.4.0.15, EMC VASA Virtual Appliance versions prior to 8.4.0.512, and EMC VMAX Embedded Management (eManagement) versions prior to and including 1.4 (Enginuity Release 5977.1125.1125 and earlier) contain an authentication bypass vulnerability that may potentially be exploited by malicious users to compromise the affected system.
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 confidenceThis is an authentication bypass vulnerability in multiple EMC virtual appliance products (Unisphere for VMAX, Solutions Enabler, VASA, and VMAX eManagement). The vulnerability allows unauthenticated remote attackers to bypass authentication mechanisms and gain unauthorized access to the affected systems, potentially leading to complete system compromise.
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< 8.4.0.15< 8.4.0.15< 8.4.0.512<= 1.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check Unisphere for VMAX versionAccess the virtual appliance management interface or check the installed package/version through the vApp console. Typically found in About or System Information section of the web UI, or via command line: 'emcpreg -list' or checking version files in /opt/emc/unicenter/Affected if Version is earlier than 8.4.0.15 and the Unisphere web interface is accessible over network
-
Check Solutions Enabler versionRun 'symcfg -version' or 'se_version' command on the virtual appliance, or check through the Solutions Enabler management interfaceAffected if Version is earlier than 8.4.0.15 and Solutions Enabler services are network-accessible
-
Check VASA Provider versionAccess the VASA virtual appliance management console or check via VASA Provider registration interface in vCenter. Version is typically visible in the 'About' section of VASA or in /opt/vasa/ version filesAffected if Version is earlier than 8.4.0.512 and VASA Provider is registered and accessible to vCenter
-
Check VMAX eManagement versionAccess the eManagement web interface and navigate to System > About, or check via command line on the appliance: 'emcgui -version' or inspect version files in the installation directoryAffected if Version is 1.4 or earlier and the eManagement web interface is network-accessible
-
Verify network exposure of management interfacesReview firewall rules and network segmentation to determine if the Unisphere, Solutions Enabler, VASA, or eManagement web interfaces are exposed to untrusted networks or the internet. Check listening ports (typically 8443, 443, 8080 for web interfaces)Affected if Any of the affected product interfaces are accessible from untrusted networks without additional authentication controls
The environment is affected if any of these products are installed at a version below the fixed releases (Unisphere/Solutions Enabler < 8.4.0.15, VASA < 8.4.0.512, VMAX eManagement <= 1.4) AND the respective management interfaces are network-accessible.
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.
dbcve · scoped8.4.0.158.4.0.512
Apply the vendor-provided patches: update Unisphere for VMAX vApp and Solutions Enabler Virtual Appliance to version 8.4.0.15 or later, VASA Virtual Appliance to version 8.4.0.512 or later, and VMAX eManagement to a version beyond 1.4 (post-Enginuity Release 5977).
Unisphere: 8.4.0.15+ | Solutions Enabler: 8.4.0.15+ | VASA: 8.4.0.512+ | VMAX eManagement: >1.4
- Identify which EMC product(s) are deployed (Unisphere, Solutions Enabler, VASA, or VMAX eManagement)
- Check the current version of the affected product
- For EMC Unisphere: upgrade to version 8.4.0.15 or later
- For EMC Solutions Enabler: upgrade to version 8.4.0.15 or later
- For EMC VASA: upgrade to version 8.4.0.512 or later
- For EMC VMAX Embedded Management (eManagement): upgrade to a version greater than 1.4
- After upgrade, verify the new version is installed and the authentication bypass is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14375 — 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-14375 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