CVE-2017-12711
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 · uneditedAn Incorrect Privilege Assignment issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. A built-in user account has been granted a sensitive privilege that may allow a user to elevate to administrative privileges.
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 confidenceAdvantech WebAccess versions prior to V8.2_20170817 contain a built-in user account that has been incorrectly granted a sensitive privilege, allowing a standard user to escalate their privileges to administrative level.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 WebAccess versionLocate the Advantech WebAccess installation directory and check the version information file, or use the WebAccess dashboard to view the software version under Help or About sectionAffected if The version displayed is earlier than V8.2_20170817 or shows version 8.2 without the dated build identifier
-
Locate built-in user accountsAccess the WebAccess user management interface (typically under User Manager or Configuration > User Administration) and enumerate all accounts marked as built-in or system accountsAffected if A built-in or default system account exists alongside normal user accounts
-
Examine account privilege assignmentsReview the security permissions or role assignments for each built-in account identified, checking whether they are assigned to Administrator, Super User, or equivalent high-privilege rolesAffected if Any built-in account is assigned administrative-level privileges or roles
-
Test standard user privilege escalationLog in with a standard (non-administrator) user account and attempt to access administrative functions, configuration files, or system settings that should require elevated privilegesAffected if A standard user can access or modify settings that should be restricted to administrators
-
Review account audit logsCheck WebAccess logs for any instances where built-in accounts were used to perform administrative actions, or where privilege escalation occurredAffected if Logs show built-in accounts performing administrative tasks or successful privilege escalation events
You are affected if WebAccess version is prior to V8.2_20170817 AND a built-in account exists with administrative privileges that allows standard users to escalate their access level.
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 to WebAccess version V8.2_20170817 or later to receive the vendor patch, or identify and remove/disable the overly-privileged built-in account while implementing least-privilege access controls.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12711 — 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-12711 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