CVE-2017-12694
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 Directory Traversal issue was discovered in SpiderControl SCADA Web Server. An attacker may be able to use a simple GET request to perform a directory traversal into system files.
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 directory traversal vulnerability in SpiderControl SCADA Web Server allows remote attackers to use crafted GET requests with path traversal sequences (e.g., ../../../) to access files outside the web root directory, potentially exposing sensitive system files, configuration data, or credentials.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 if SpiderControl SCADA Web Server is installedCheck for SpiderControl web server processes running on the system (common ports: 80, 443, 8080, 8443) or look for installation directories containing 'SpiderControl' in the program files. On Windows, check the Services list for SpiderControl services. On Linux, check for spidermw or similar daemon processes.Affected if SpiderControl SCADA Web Server is installed and running on the system
-
Verify web server is network accessibleUse a browser or curl command to access the web server HTTP interface. For example: curl -v http://TARGET_IP:PORT/ where PORT is the web server port (commonly 80 or 8080).Affected if The SpiderControl web interface is reachable over the network (even on localhost)
-
Test for directory traversal vulnerabilitySend a crafted GET request with path traversal sequences to attempt to access files outside the web root. For example: curl -v http://TARGET_IP:PORT/../../../windows/win.ini or curl -v http://TARGET_IP:PORT/../../../etc/passwd (adjust path depth as needed).Affected if The server returns content from files outside the intended web root directory, indicating successful directory traversal
-
Check for exposure to untrusted networksReview firewall rules and network configuration to determine if the SpiderControl web server HTTP/HTTPS ports are accessible from untrusted networks or the internet rather than only from trusted internal networks.Affected if The web server port is open to untrusted networks or the internet without proper access controls
-
Review access logs for exploitation attemptsExamine SpiderControl web server access logs for requests containing '../' sequences, path traversal patterns, or attempts to access system files like win.ini, passwd, or config files.Affected if Historical or current logs show directory traversal attempts against the web server
If SpiderControl SCADA Web Server is installed and its web interface is accessible, the environment is affected since all versions contain the directory traversal vulnerability.
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 dataImplement strict input validation on all file path parameters using allow-lists, normalize paths before processing, and configure the web server to restrict file access to intended directories only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12694 — 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-12694 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