CVE-2017-13997
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 Missing Authentication for Critical Function issue was discovered in Schneider Electric InduSoft Web Studio v8.0 SP2 or prior, and InTouch Machine Edition v8.0 SP2 or prior. InduSoft Web Studio provides the capability for an HMI client to trigger script execution on the server for the purposes of performing customized calculations or actions. A remote malicious entity could bypass the server authentication and trigger the execution of an arbitrary command. The command is executed under high privileges and could lead to a complete compromise of the server.
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 confidenceThis is a critical authentication bypass vulnerability in Schneider Electric's InduSoft Web Studio and InTouch Machine Edition (v8.0 SP2 and prior). The HMI client script execution functionality lacks proper authentication controls, allowing remote unauthenticated attackers to bypass server authentication and execute arbitrary commands with high privileges, leading to complete server compromise.
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.
-
Identify installed InduSoft Web Studio or InTouch Machine Edition versionCheck the installed software version through the Windows Programs and Features control panel, or locate the application executable (typically in C:\Program Files\Schneider Electric\InduSoft Web Studio v8\ or similar path) and view its version properties. Compare the version number to the affected range (8.0 and prior, including SP1 and SP2).Affected if The installed version is 8.0 or any version prior to 8.0, including service packs SP1 and SP2.
-
Confirm the application is the vulnerable Schneider Electric productVerify the specific product name in the installed programs list matches either 'Wonderware InduSoft Web Studio' or 'Wonderware InTouch Machine Edition'. Both products share the same vulnerability in affected versions.Affected if The installed product is Schneider Electric Wonderware InduSoft Web Studio or Wonderware InTouch Machine Edition version 8.0 or earlier.
-
Determine if the HMI web service is running and accessibleCheck if the application's built-in web server or HMI service is active by reviewing running services or checking for listening ports associated with the software (default web ports 80, 443, or custom ports used by the application). Use 'netstat -an' or review the application configuration for enabled web listening features.Affected if The HMI web service is enabled and accessible from network segments where untrusted users could reach it.
-
Review application logs for unauthorized script executionExamine InduSoft Web Studio or InTouch Machine Edition runtime logs, event logs, and script execution history for entries indicating script execution without corresponding authenticated operator actions. Look for commands or scripts originating from unexpected IP addresses or users.Affected if Logs show script execution or command invocations that do not correspond to known legitimate operator sessions or originated from unauthenticated remote sources.
You are affected if Schneider Electric InduSoft Web Studio or InTouch Machine Edition version 8.0 or earlier is installed and the HMI web service is network-accessible, as this combination allows remote unauthenticated attackers to bypass authentication and execute commands.
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.
dbcve · scopedUpgrade to a patched version beyond v8.0 SP2, implement network segmentation to isolate HMI systems from untrusted networks, and apply compensating controls such as firewalls to restrict access to the affected service.
InduSoft Web Studio v8.1 or later / InTouch Machine Edition v8.1 or later
- Download InduSoft Web Studio version 8.1 or later from the Schneider Electric website or official distribution channel
- Verify the download using checksums provided by Schneider Electric
- Back up all project files, application configurations, and runtime databases before upgrading
- Stop all running InduSoft Web Studio services and InTouch applications
- Install the new version following the standard installation procedure
- Restore project files from the backup if needed
- Start the services and verify the application functions correctly
- Validate that the security fix is applied by reviewing the release notes or security bulletin for the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13997 — 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-13997 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