CVE-2017-14019
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 Unquoted Search Path or Element issue was discovered in Progea Movicon Version 11.5.1181 and prior. An unquoted search path or element vulnerability has been identified, which may allow an authorized local user to insert arbitrary code into the unquoted service path and escalate his or her 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 confidenceProgea Movicon Version 11.5.1181 and prior contains an unquoted service path vulnerability that allows an authorized local user to inject arbitrary code into the service executable path and escalate privileges to higher levels.
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= 11.5.1181CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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.
-
Identify Movicon installation and versionCheck the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Movicon or check Program Files for Progea\Movicon folder, then locate the version information in the application's About or readme filesAffected if Installed version is 11.5.1181 or any prior version (11.5.x before 11.5.1181)
-
Enumerate Movicon-related Windows servicesOpen Services console (services.msc) or run 'sc queryex type= service state= all' and filter for services with 'Movicon' in the name or pathAffected if Any Movicon-related Windows service exists on the system
-
Check service executable paths for unquoted pathsFor each Movicon service found, run 'sc qc [ServiceName]' to query the binary path, or use 'wmic service get name,pathname' and inspect if the path contains spaces and lacks quotation marksAffected if The service BINARY_PATH_NAME contains spaces and is not enclosed in quotation marks
-
Verify service is running with elevated privilegesRun 'sc qc [ServiceName]' and check the START_TYPE and SECURITY_DESCRIPTOR fields, or check the service properties in services.msc to confirm it runs under SYSTEM or a privileged accountAffected if The vulnerable unquoted service runs under SYSTEM, LocalSystem, or another high-privilege account
A system is affected if Progea Movicon version 11.5.1181 or prior is installed and any Movicon Windows service has an unquoted executable path containing spaces, allowing potential privilege escalation.
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 vendor patch or update to a patched version of Movicon; if no patch available, review and harden service configuration, restrict local user permissions, and monitor for suspicious binary placement in service directories.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14019 — 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-14019 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