CVE-2017-12707
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 SpiderControl SCADA MicroBrowser Versions 1.6.30.144 and prior. Opening a maliciously crafted html file may cause a stack overflow.
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 confidenceA stack-based buffer overflow vulnerability exists in SpiderControl SCADA MicroBrowser versions 1.6.30.144 and prior. The vulnerability is triggered when the application opens a maliciously crafted HTML file, causing a stack overflow that could potentially allow arbitrary code execution, as indicated by the critical CVSS score of 9.8.
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.6.30.144CVSS 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.
-
Locate SpiderControl SCADA MicroBrowser installationSearch for the SpiderControl MicroBrowser executable or installation directory on the system, typically found in Program Files or SCADA application foldersAffected if The MicroBrowser application is installed on the system
-
Identify the installed version numberRight-click the MicroBrowser executable, select Properties, and check the Version tab, or look for a version file in the installation directoryAffected if The reported version is 1.6.30.144 or lower
-
Compare version to affected rangeCompare your installed version against the affected range: any version less than or equal to 1.6.30.144 is vulnerableAffected if Installed version is 1.6.30.144 or any prior version
-
Verify MicroBrowser component is accessibleCheck if the MicroBrowser component is exposed through web interfaces, SCADA HMI panels, or other access points where untrusted HTML files could be openedAffected if The MicroBrowser can be used to open HTML files from untrusted sources
-
Review access to untrusted HTML filesDetermine whether the MicroBrowser has access to open HTML files from network shares, USB drives, or other untrusted locationsAffected if Users can open HTML files from untrusted or external sources in the MicroBrowser
The system is affected if SpiderControl SCADA MicroBrowser version 1.6.30.144 or lower is installed and users can open HTML files through it.
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 dataUpdate SpiderControl SCADA MicroBrowser to a version newer than 1.6.30.144. Until patched, avoid opening untrusted or malicious HTML files in the MicroBrowser application.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12707 — 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-12707 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