CVE-2017-6033
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 · uneditedA DLL Hijacking issue was discovered in Schneider Electric Interactive Graphical SCADA System (IGSS) Software, Version 12 and previous versions. The software will execute a malicious file if it is named the same as a legitimate file and placed in a location that is earlier in the search path.
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 confidenceSchneider Electric IGSS versions 12 and prior are vulnerable to DLL hijacking. The application loads DLLs without specifying full paths, allowing attackers to place malicious DLLs with legitimate names in directories earlier in the search order, 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<= 12.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/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.
-
Locate IGSS installation directoryCheck common installation paths such as C:\Program Files\Schneider Electric\IGSS or C:\IGSS, or search for igss.exe in the system using 'where /r C:\ igss.exe'Affected if IGSS executable is found on the system
-
Determine installed IGSS versionRight-click on the igss.exe file, select Properties, and check the Version tab for the product version. Alternatively, open IGSS and navigate to Help > About to view version information.Affected if Version displayed is 12.0 or any version prior to 12.0
-
Verify PATH environment variable configurationOpen System Properties > Advanced > Environment Variables and review the PATH variable for user and system. Check if IGSS installation directory or any writable directory appears in PATH.Affected if IGSS installation folder or writable directories are present in the system PATH before the Windows system directories
-
Check for writable directories in PATH orderOpen Command Prompt and run 'echo %PATH%' to display PATH entries in order. For each directory, right-click in Explorer to check if standard users have write permissions.Affected if Any directory listed earlier in PATH than Windows\System32 is writable by non-admin users
-
Confirm IGSS loads external DLLsUse a process monitor tool such as Sysinternals Process Monitor to trace DLL load attempts when IGSS starts. Filter by process name igss.exe and look for LoadLibrary events.Affected if IGSS attempts to load DLLs from directories without full paths, especially from directories in the user-writable PATH locations
The system is affected if Schneider Electric IGSS version 12.0 or prior is installed and the application loads DLLs without full paths while the PATH contains writable directories earlier in the search order.
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 when available; meanwhile, remove unnecessary writeable directories from system PATH, restrict user write access to IGSS installation folders, and implement application whitelisting to prevent unauthorized DLL loading.
- 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-6033 — 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-6033 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