CVE-2017-6051
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 BLF-Tech LLC VisualView HMI Version 9.9.14.0 and prior. The uncontrolled search path element vulnerability has been identified, which may allow an attacker to run a malicious DLL file within the search path resulting in execution of arbitrary code.
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 confidenceBLF-Tech LLC VisualView HMI versions 9.9.14.0 and prior contain an uncontrolled search path element vulnerability (DLL hijacking). The application uses an uncontrolled search path when loading dynamic-link libraries, allowing an attacker to place a malicious DLL file in a directory within the search path (such as the application directory or system paths) which will be loaded and executed with the application's privileges, resulting in arbitrary code execution.
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<= 9.9.14.0CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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 VisualView HMI installed versionLocate the VisualView HMI installation directory (typically under C:\Program Files\Blftech or C:\Program Files (x86)\Blftech). Right-click on the main executable (commonly VisualView.exe or similar) and select Properties, then check the Details tab for the Product Version field.Affected if The displayed version number is 9.9.14.0 or lower (for example, 9.9.14.0, 9.9.13.5, 9.9.10.0, etc.)
-
Confirm exact version from applicationIf available, launch the VisualView HMI application and navigate to its Help > About or Settings > Version section to view the precise installed build number.Affected if The version shown is less than or equal to 9.9.14.0
-
Inspect DLL search path configurationCheck the application executable for manifest or configuration that specifies Safe DLL Search Mode. Use a tool like Process Monitor or examine if the application calls SetDllDirectory or specifies absolute paths when loading DLLs. If the app loads DLLs using only relative paths without safe search order, it is likely vulnerable.Affected if The application uses relative paths for DLL loading without explicit safe DLL search order settings (no use of SetDllDirectory, no LOAD_WITH_ALTERED_SEARCH_PATH, and no application manifest with safeDllSearchMode)
-
Audit file system permissions on application directoryReview permissions on the VisualView HMI installation folder. Check which user accounts and groups have Write or Modify access to the directory. Use icacls command (e.g., icacls "C:\Program Files\Blftech\VisualView") to list effective permissions.Affected if Any untrusted or low-privilege user account has Write or Modify permissions to the application directory, allowing placement of malicious DLL files
You are affected if VisualView HMI version is 9.9.14.0 or lower AND the application uses an uncontrolled DLL search path with writable application directories where an attacker could plant a malicious DLL.
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 any vendor patch or upgrade to a version beyond 9.9.14.0. If no patch is available, restrict write access to application directories, implement application whitelisting, and use secure DLL search order settings to mitigate DLL planting attacks.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6051 — 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-6051 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