CVE-2017-9967
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 security misconfiguration vulnerability exists in Schneider Electric's IGSS SCADA Software versions 12 and prior. Security configuration settings such as Address Space Layout Randomization (ASLR) and Data Execution prevention (DEP) were not properly configured resulting in weak security.
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 · moderate confidenceThis vulnerability is a security misconfiguration in Schneider Electric IGSS SCADA Software versions 12 and prior, where Windows memory protection mechanisms ASLR and DEP are not properly enabled. This weakens the system's defenses against memory corruption exploits, allowing attackers to more easily execute arbitrary code via buffer overflows or similar attacks.
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
- 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.
-
Identify IGSS versionLocate the installed IGSS SCADA software and determine its version number. This can typically be found in the program's About section, installation directory, or Windows Add/Remove Programs. Compare the installed version against the affected range: version 12.0 and prior.Affected if The installed version is 12.0 or any prior version.
-
Verify Windows ASLR is enabled at OS levelOpen Windows System Properties or use the command 'bcdedit /enum' to check if Address Space Layout Randomization is enabled system-wide. Alternatively, check the registry key HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management for 'MoveImages' value.Affected if ASLR is disabled or not properly configured at the Windows operating system level.
-
Verify Windows DEP is enabled at OS levelOpen Windows System Properties via Control Panel > System > Advanced > Performance Settings > Data Execution Prevention, or run 'wmic OS Get DataExecutionPrevention_SupportPolicy' to check the DEP policy setting.Affected if DEP is disabled or set to a policy that does not cover all programs and services.
-
Confirm IGSS processes use memory protectionsUse Windows Task Manager or Process Explorer to view the IGSS executable (typically igss.exe or related .exe files) and verify that ASLR and DEP are applied to these processes. You can use 'dumpbin /headers' on IGSS binaries to check for ASLR flag in the PE headers, or use a tool like Process Explorer to verify memory protection settings.Affected if IGSS executable files do not have ASLR enabled in their PE headers, or running processes do not have DEP applied.
You are affected if IGSS version 12.0 or prior is installed AND either ASLR or DEP is not properly enabled at the Windows level or applied to IGSS processes.
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 dataEnable Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) in the Windows operating system and verify IGSS application settings properly leverage these protections. Test thoroughly to ensure SCADA functionality remains intact.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9967 — 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-9967 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