CVE-2017-12710
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 SQL Injection issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. By submitting a specially crafted parameter, it is possible to inject arbitrary SQL statements that could allow an attacker to obtain sensitive information.
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 confidenceAdvantech WebAccess versions prior to V8.2_20170817 contain a SQL injection vulnerability in their web interface. Attackers can submit specially crafted parameters containing malicious SQL statements, allowing them to inject arbitrary queries into the backend database and potentially extract sensitive information including user credentials, system configurations, or other stored data.
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.2CVSS 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.
-
Confirm Advantech WebAccess installationLocate the WebAccess installation directory or check installed programs on the system. Common installation paths include C:\Advantech\WebAccess or C:\Inetpub\wwwroot\WebAccess. Check for the presence of WebAccess DLLs, configuration files, or the WebAccess Dashboard application.Affected if Advantech WebAccess is installed on the system
-
Identify installed WebAccess versionLocate version information in the installation directory. Check files such as version.ini, about.htm, or the main executable properties. The version may also be displayed in the web interface login page or dashboard. Compare the discovered version string to the affected range.Affected if The installed version is any release prior to V8.2_20170817, or version 8.2 and earlier
-
Verify web interface is enabledCheck if the WebAccess web service is running. This can be done by attempting to access the web interface via browser (typically port 80 or 443), checking IIS or the Windows service manager for WebAccess services, or reviewing the web server configuration files.Affected if The web interface is accessible and responds to HTTP/HTTPS requests
-
Confirm database connectivity configurationReview the WebAccess configuration files to confirm the application is connected to a backend database (such as Microsoft SQL Server). The SQL injection vulnerability affects the database query handling in the web interface.Affected if The application is configured with a backend database for storing user credentials, system configurations, or application data
A system is affected if Advantech WebAccess version 8.2 or earlier is installed with the web interface enabled and connected to a database, as the SQL injection flaw can be exploited through crafted HTTP parameters.
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 Advantech WebAccess to version V8.2_20170817 or later to patch the SQL injection vulnerability. As a temporary control, implement web application firewall rules to detect and block SQL injection attempts in HTTP parameters.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12710 — 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-12710 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