CVE-2018-11063
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 · uneditedDell WMS versions 1.1 and prior are impacted by multiple unquoted service path vulnerabilities. Affected software installs multiple services incorrectly by specifying the paths to the service executables without quotes. This could potentially allow a low-privileged local user to execute arbitrary executables with elevated privileges.
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 confidenceDell WMS versions 1.1 and prior contain multiple unquoted service path vulnerabilities where service executables are installed without quotation marks around their file paths. This allows a low-privileged local attacker to place a malicious executable in an intermediate directory within the service path, which will be executed with elevated (SYSTEM) privileges when the service starts.
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<= 1.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Confirm Dell Wyse Management Suite installation and versionCheck the installed version of Dell Wyse Management Suite. This can be done via Windows Programs and Features, or by querying the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries related to Dell Wyse Management Suite or WMS.Affected if The installed version is 1.1 or any version prior to 1.1.
-
Identify Dell WMS Windows servicesList all Windows services with names or paths containing references to Dell, Wyse, or WMS. Use 'sc query' or review services via Services.msc. Look for any service where the executable path points to Dell installation directories.Affected if Any Dell Wyse Management Suite services are found on the system.
-
Inspect service executable paths for unquoted pathsFor each identified Dell WMS service, run 'sc qc <service_name>' to query the service configuration. Examine the BINARY_PATH_NAME field. Check if the path contains spaces but is not enclosed in quotation marks.Affected if The BINARY_PATH_NAME shows a path with spaces that is NOT wrapped in quotation marks (e.g., C:\Program Files\Dell\WMS\service.exe instead of "C:\Program Files\Dell\WMS\service.exe").
-
Check write permissions on intermediate directories in unquoted pathsFor any service with an unquoted path containing spaces, identify each directory in the path (e.g., for C:\Program Files\Dell\WMS\service.exe, check Program Files, Dell, and WMS directories). Use icacls or file explorer properties to verify which users have Write or Write+Execute permissions on each directory.Affected if A low-privilege user account has Write permission to any intermediate directory in an unquoted service path, allowing placement of a malicious executable.
The system is affected if Dell Wyse Management Suite version 1.1 or prior is installed AND at least one service has an unquoted executable path where an attacker-controlled intermediate directory has weak permissions.
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 dataCorrect all affected service configurations to use quoted executable paths, or reinstall the software with proper service configurations; additionally, restrict write access to directories in the service paths to prevent exploitation.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11063 — 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-2018-11063 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