CVE-2017-9661
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 SIMPlight SCADA Software version 4.3.0.27 and prior. The uncontrolled search path element vulnerability has been identified, which may allow an attacker to place 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 confidenceSIMPlight SCADA Software versions 4.3.0.27 and prior contain an uncontrolled search path element vulnerability in DLL loading. The application uses an insecure DLL search order, allowing attackers to place a malicious DLL with a matching name in a directory earlier in the search path (typically the application working directory), causing arbitrary code execution when the application loads the trojaned DLL.
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<= 4.3.0.27CVSS 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 SIMPlight SCADA versionLocate the SIMPlight SCADA installation directory and check the version information, typically found in the executable properties or an about dialog within the applicationAffected if The installed version is 4.3.0.27 or lower
-
Check working directory writabilityInspect the permissions on the SIMPlight SCADA application working directory (where the main executable runs from) to determine if unprivileged users have write accessAffected if The application directory is writable by users who should not have administrative privileges, allowing DLL planting
-
Verify DLL search path includes working directoryExamine the application configuration or use process monitoring tools to observe whether the DLL search path includes the application working directory before system pathsAffected if The DLL search order includes the application working directory, enabling malicious DLL loading from that location
-
Check for writable subdirectories in installation pathReview file system permissions on all subdirectories within the SIMPlight SCADA installation folderAffected if Any directory in the search path preceding system directories is writable by non-admin users
A user is affected if SIMPlight SCADA version is 4.3.0.27 or lower AND the application directory or any directory earlier in the DLL search path is writable by unprivileged users, allowing DLL hijacking.
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 dataImplement secure DLL loading by specifying fully qualified paths for all DLL imports, removing the application directory from the DLL search path using SetDllDirectory(NULL), and ensuring the application directory is not writable by unprivileged users to prevent DLL planting attacks.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9661 — 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-9661 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