CVE-2017-9970
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 remote code execution vulnerability exists in Schneider Electric's StruxureOn Gateway versions 1.1.3 and prior. Uploading a zip which contains carefully crafted metadata allows for the file to be uploaded to any directory on the host machine information which could lead to remote code execution.
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 confidenceA path traversal vulnerability in StruxureOn Gateway versions 1.1.3 and prior allows attackers to upload malicious zip files containing crafted metadata that can write files to arbitrary directories on the host system, leading to remote 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<= 1.1.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 StruxureOn Gateway installationLocate the StruxureOn Gateway application on the system. Check for its installation directory, service, or web interface. On Windows, look in Program Files; on Linux, check /opt or standard application directories.Affected if StruxureOn Gateway is installed on the system
-
Determine installed versionAccess the StruxureOn Gateway web interface and navigate to the About or System Information page. Alternatively, check the installation directory for a version file or examine the service executable properties.Affected if The version displayed is 1.1.3 or any version prior to 1.1.3
-
Verify upload functionality is accessibleCheck if the file upload or import feature is available and accessible in the StruxureOn Gateway web interface. Look for features related to firmware updates, configuration imports, or backup restoration.Affected if The upload or import functionality is exposed and accessible to users or attackers
-
Check network exposureExamine network configuration to determine if the StruxureOn Gateway web interface is accessible from untrusted networks. Review firewall rules and access control lists.Affected if The web interface is exposed to the internet or untrusted internal networks without proper access controls
-
Review upload directory permissionsInspect the configuration to confirm that uploaded files are stored in a directory with weak permissions or that path traversal in uploaded archives is not being validated.Affected if The upload directory allows write access to arbitrary paths or path traversal validation is missing
-
Examine uploaded zip file handlingIf log files are available, review them for any zip upload requests. Check if the system extracts uploaded zip files without validating the file paths within the archive.Affected if The system extracts zip files from untrusted sources without validating contained file paths
A system is affected if StruxureOn Gateway version 1.1.3 or prior is installed and the upload or import feature is accessible, as the path traversal vulnerability can be exploited through malicious zip file metadata.
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 dataUpgrade StruxureOn Gateway to a version newer than 1.1.3. If upgrading is not immediately possible, implement strict validation on uploaded zip files to prevent path traversal and restrict upload directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9970 — 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-9970 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