CVE-2017-14384
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 Dell Storage Manager versions earlier than 16.3.20, the EMConfigMigration service is affected by a directory traversal vulnerability. A remote malicious user could potentially exploit this vulnerability to read unauthorized files by supplying specially crafted strings in input parameters of the application. A malicious user cannot delete or modify any files via this 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 confidenceA directory traversal vulnerability exists in the EMConfigMigration service of Dell Storage Manager versions prior to 16.3.20. Remote attackers can supply specially crafted path sequences (e.g., ../) in input parameters to read files outside the intended application directory, potentially exposing sensitive system files.
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< 16.3.20CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dell Storage Manager versionUse the software inventory or about section within the Dell Storage Manager application interface, or check the installed programs list on the server where DSM is deployedAffected if The discovered version number is lower than 16.3.20 (for example, 16.3.10, 16.2.x, or earlier)
-
Locate the EMConfigMigration serviceOn the Dell Storage Manager server, open Windows Services or use command 'sc query' to find the EMConfigMigration service and confirm its running stateAffected if The EMConfigMigration service exists and is running on a version of Dell Storage Manager prior to 16.3.20
-
Verify network accessibility of EMConfigMigrationReview firewall rules and network configuration to determine if the EMConfigMigration service port (typically the DSM server port) is exposed to untrusted networks or the internetAffected if The service port is accessible from outside the trusted internal network and the DSM version is below 16.3.20
-
Inspect application logs for path traversal attemptsSearch Dell Storage Manager logs for patterns containing '../' or '..\' sequences in request parameters, particularly around the EMConfigMigration functionalityAffected if Suspicious traversal sequences appear in logs and the DSM version is below 16.3.20
A system is affected if Dell Storage Manager version is confirmed to be lower than 16.3.20 and the EMConfigMigration service is active, regardless of whether exploitation is observed.
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 data16.3.20
Upgrade Dell Storage Manager to version 16.3.20 or later. If immediate patching is not possible, implement input validation and sanitization on the EMConfigMigration service to reject path traversal sequences.
- 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-14384 — 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-14384 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