CVE-2017-5161
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 Sielco Sistemi Winlog Lite SCADA Software, versions prior to Version 3.02.01, and Winlog Pro SCADA Software, versions prior to Version 3.02.01. An uncontrolled search path element (DLL Hijacking) vulnerability has been identified. Exploitation of this vulnerability could give an attacker access to the system with the same level of privilege as the application that utilizes the malicious DLL.
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 confidenceDLL hijacking vulnerability in Winlog Lite/Pro SCADA software. The application uses an uncontrolled search path when loading dynamic link libraries, allowing an attacker to place a malicious DLL in a directory searched by the application (e.g., current working directory) to achieve code execution with the same privileges as the application.
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<= 3.01.10<= 3.01.10CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/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 installed Winlog versionLocate the Winlog installation directory (commonly C:\Program Files\Sielcosistemi\Winlog or C:\Program Files (x86)\Sielcosistemi\Winlog). Right-click on Winlog.exe, select Properties, and check the Details tab for the File Version. Alternatively, check the version in the Windows Registry under HKLM\SOFTWARE\Sielcosistemi\Winlog or HKLM\SOFTWARE\WOW6432Node\Sielcosistemi\Winlog.Affected if The reported version is 3.01.10 or lower.
-
Determine if application runs from user-writable locationCheck the shortcut or service configuration that launches Winlog. Note the 'Start in' folder specified in the shortcut properties, or the working directory if launched as a service. Verify if this directory is writable by non-privileged users.Affected if The application launches from or uses a directory where standard users can create or modify files, such as the current working directory, a shared network folder, or a user-writable application folder.
-
Check for vulnerable DLL loading behaviorObserve which DLLs Winlog attempts to load at startup using process monitoring tools (such as Sysinternals Process Monitor). Filter by process name Winlog.exe and look for DLL load attempts that fail or succeed from unexpected paths.Affected if The application loads DLLs from the current working directory, application directory, or other locations in the search path without using safe DLL search mode.
-
Verify DLL search path configurationCheck if the application sets the SETDLLDIRECTORY flag or uses safe DLL search mode. Review the application configuration files in the Winlog installation directory for any custom DLL path settings.Affected if The application does not explicitly set secure DLL loading paths and relies on the default Windows DLL search order, allowing loading from the current directory.
You are affected if Winlog Lite or Pro version 3.01.10 or lower is installed and the application runs from or accesses directories where unprivileged users can place malicious DLL files.
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 Winlog Lite/Pro version 3.02.01 or later. As compensating controls, run the application with least privilege, ensure proper file permissions on application directories, and restrict write access to directories in the DLL search order.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5161 — 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-5161 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