CVE-2017-14017
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 Uncontrolled Search Path Element issue was discovered in Progea Movicon Version 11.5.1181 and prior. An uncontrolled search path element vulnerability has been identified, which may allow a remote attacker without privileges to execute arbitrary code in the form of a malicious DLL file.
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 a DLL hijacking vulnerability (uncontrolled search path element) in Progea Movicon SCADA software version 11.5.1181 and prior. The application loads DLLs from insecure search paths, allowing an unauthenticated remote attacker to place a malicious DLL in a location where the application will load it, executing arbitrary code with the application's privileges.
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
- 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.
-
Detect Progea Movicon installationCheck for Movicon installation by searching for the Movicon executable (e.g., Movicon.exe) in common installation paths such as C:\Program Files\Progea or C:\Program Files (x86)\Progea, or query the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Progea or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Progea for the installed product key.Affected if Progea Movicon is found installed on the system.
-
Determine installed versionRight-click on the Movicon.exe file in the installation directory, select Properties, and check the Details tab for the Product Version. Alternatively, query the registry key where the installation path is stored and append \Movicon.exe to read its version information.Affected if The version number is 11.5.1181 or lower.
-
Verify directory permissionsRight-click on the Progea Movicon installation folder, select Properties, then go to the Security tab. Click on Advanced to view detailed permissions. Check whether users without administrative privileges have Write or Modify permissions to this folder.Affected if Non-privileged users have Write or Modify access to the Movicon installation directory.
-
Inspect for suspicious DLLsEnumerate all DLL files present in the Progea Movicon installation directory. Compare the list against known legitimate Movicon DLLs or check file properties (right-click, Properties, Details) to identify any DLLs that are not part of the standard installation or that appear unexpected.Affected if Unexpected or unknown DLL files exist in the Movicon installation directory.
The environment is affected if Progea Movicon version 11.5.1181 or lower is installed and the installation directory grants non-privileged users write access, allowing an attacker to place a malicious DLL for the application to load.
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 dataUpgrade to a patched version of Progea Movicon. If no patch is available, secure the application directory and remove write access for non-privileged users to prevent placement of malicious DLLs.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14017 — 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-14017 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