CVE-2017-12713
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 Permission Assignment for Critical Resource issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. Multiple files and folders with ACLs that affect other users are allowed to be modified by non-administrator accounts.
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 incorrect Windows Access Control List (ACL) permissions on multiple critical files and folders, allowing unprivileged users to modify ACLs that should be restricted to administrators. This could enable privilege escalation or tampering with system components.
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.
-
Confirm Advantech WebAccess installationCheck for WebAccess installation by looking in typical installation paths such as C:\inetpub\wwwroot\BroadWeb or C:\Program Files\Advantech\WebAccess, or search for the 'WebAccess' folder in the file system.Affected if Advantech WebAccess is found on the system
-
Identify installed WebAccess versionLocate the version information in the installation directory, typically in a version.txt file, or check the Windows Programs and Features list for the installed version of Advantech WebAccess.Affected if The installed version is 8.2 or earlier, or the version cannot be determined to be later than 8.2_20170817
-
Verify ACL permissions on WebAccess root directoryRight-click the WebAccess installation folder, select Properties, then Security tab. Check the permissions for Users or non-admin groups. Verify if they have Full Control, Modify, or Write permissions that should not be granted to non-administrators.Affected if Non-administrator users have Full Control, Modify, or Write permissions on the WebAccess root directory
-
Inspect ACL permissions on configuration foldersExamine ACLs on subfolders such as config, cfg, or scripts directories under the WebAccess installation path. Use icacls.exe or the Security tab in folder properties to list effective permissions for standard users.Affected if Non-privileged users can modify ACL settings or have write access to configuration directories that should be admin-only
-
Check for excessive permissions on executable directoriesReview permissions on folders containing .exe or .dll files (such as bin or runtime directories). Verify that Users group does not have Write or Modify permissions to these locations.Affected if Standard users have Write or Modify access to directories containing WebAccess executables or DLLs
A user is affected if Advantech WebAccess version 8.2 or earlier is installed AND non-administrator accounts have been granted excessive file system permissions (Write, Modify, or ACL modification rights) on WebAccess directories or critical system files.
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 to WebAccess V8.2_20170817 or later, or manually review and correct file/folder ACLs to ensure non-administrator accounts cannot modify protected system resources.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12713 — 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-12713 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