CVE-2017-14024
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 Stack-based Buffer Overflow issue was discovered in Schneider Electric InduSoft Web Studio v8.0 SP2 Patch 1 and prior versions, and InTouch Machine Edition v8.0 SP2 Patch 1 and prior versions. The stack-based buffer overflow vulnerability has been identified, which may allow remote code execution with high privileges.
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 confidenceStack-based buffer overflow vulnerability in Schneider Electric InduSoft Web Studio v8.0 SP2 Patch 1 and prior, and InTouch Machine Edition v8.0 SP2 Patch 1 and prior. The overflow allows remote code execution with high privileges.
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<= 8.0<= 8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Verify InduSoft Web Studio installationSearch for InduSoft Web Studio installation directories such as C:\Program Files\Schneider Electric\InduSoft Web Studio\ or C:\Program Files (x86)\InduSoft Web Studio\. Check the Windows registry under HKLM\SOFTWARE\InduSoft or HKLM\SOFTWARE\WOW6432Node\InduSoft for installation paths.Affected if Schneider Electric InduSoft Web Studio is found installed on the system.
-
Verify InTouch Machine Edition installationSearch for InTouch Machine Edition installation directories such as C:\Program Files\Schneider Electric\InTouch Machine Edition\ or C:\Program Files (x86)\Wonderware\InTouch Machine Edition\. Check the Windows registry under HKLM\SOFTWARE\Wonderware or HKLM\SOFTWARE\Schneider Electric for installation entries.Affected if Schneider Electric Wonderware InTouch Machine Edition is found installed on the system.
-
Determine installed version of InduSoft Web StudioRight-click on the main executable (typically InduSoftWebStudio.exe in the installation bin folder) and select Properties, then view the Details tab for version information. Alternatively, query the Windows registry key HKLM\SOFTWARE\InduSoft\Web Studio\Version if present.Affected if The reported version is 8.0 or any version prior to 8.0 SP2 Patch 1.
-
Determine installed version of InTouch Machine EditionRight-click on the main executable (typically InTouchMachineEdition.exe in the installation folder) and select Properties, then view the Details tab for version information. Alternatively, query the Windows registry key HKLM\SOFTWARE\Wonderware\InTouch Machine Edition\Version if present.Affected if The reported version is 8.0 or any version prior to 8.0 SP2 Patch 1.
-
Assess network exposure of the affected applicationReview Windows Firewall rules and any network firewall configurations to determine if the application ports (commonly TCP 1234 for development, or configured runtime ports) are open to untrusted networks. Check if the workstation has direct connectivity to the internet or untrusted VLANs.Affected if The application is accessible from untrusted networks or the internet without network segmentation.
A system is affected if either InduSoft Web Studio or InTouch Machine Edition version 8.0 or earlier is installed and the application is network-accessible, making remote code execution possible.
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 security patch or upgrade to a version beyond v8.0 SP2 Patch 1. Isolate affected systems on network and restrict exposure to untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14024 — 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-14024 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