CVE-2017-14030
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 · uneditedAn issue was discovered in Moxa MXview v2.8 and prior. The unquoted service path escalation vulnerability could allow an authorized user with file access to escalate privileges by inserting arbitrary code into the unquoted service path.
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 confidenceMoxa MXview versions 2.8 and prior contain an unquoted service path vulnerability where the Windows service executable path contains spaces without proper quotation marks. An authorized user with file system access can place a malicious executable in an intermediate directory within the path (e.g., in a folder name before a space), causing Windows to execute it when the service starts, thereby achieving privilege escalation.
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<= 2.8CVSS 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.
-
Verify Moxa MXview installationOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed softwareAffected if Moxa MXview version 2.8 or lower appears in the installed programs list
-
Locate the MXview Windows serviceOpen Services (services.msc), locate any service with 'MXview' in the name, or run 'Get-Service | Where-Object {$_.DisplayName -like "*MXview*"}' in PowerShellAffected if A Windows service related to MXview is found
-
Check the service executable pathRight-click the MXview service > Properties > General tab, note the 'Path to executable' field. Alternatively, run 'Get-WmiObject Win32_Service | Where-Object {$_.Name -like "*MXview*"} | Select-Object Name, PathName' in PowerShellAffected if The PathName contains spaces and is not enclosed in quotation marks (e.g., C:\Program Files\Moxa\MXview\mxview.exe instead of "C:\Program Files\Moxa\MXview\mxview.exe")
-
Inspect intermediate directories in the pathFor the identified path, examine each folder name between the drive letter and the executable (e.g., if path is C:\Program Files\Moxa\MXview\mxview.exe, examine 'Program Files'), using 'Get-Acl C:\Program Files\Moxa' to check folder permissionsAffected if Any directory in the path has spaces in its name without quotes and the folder permissions allow an authorized but low-privilege user to write executables to that location
A user is affected if Moxa MXview 2.8 or earlier is installed and the Windows service path contains unquoted spaces that could allow injection of a malicious executable in an intermediate directory.
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 dataRemediate by either quoted the service executable paths in the Windows registry (adding quotes around paths with spaces) or reinstalling to a version where the vendor has addressed this issue, while restricting file system permissions to prevent unauthorized placement of executables in service-related directories.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14030 — 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-14030 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