CVE-2017-12719
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 Untrusted Pointer Dereference issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. A remote attacker is able to execute code to dereference a pointer within the program causing the application to become unavailable.
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 confidenceAn untrusted pointer dereference vulnerability in Advantech WebAccess versions prior to V8.2_20170817 allows remote attackers to dereference a pointer within the application's memory space, potentially enabling arbitrary code execution and causing the application to become unavailable.
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.2_20170817CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Advantech WebAccess installationCheck the Windows registry under HKLM\SOFTWARE\Advantech\WebAccess or look for the installation directory (commonly C:\Advantech\WebAccess or C:\Ingram\WebAccess)Affected if Advantech WebAccess is found on the system
-
Determine installed versionOpen the About or Version information within the WebAccess application, check the README.TXT in the installation directory, or inspect the version property of the WebAccess executable files (typically bwemapp.exe or related binaries)Affected if The version displayed is less than 8.2_20170817 or the version cannot be determined to be 8.2_20170817 or later
-
Verify WebAccess service is runningOpen Windows Services (services.msc) and locate the Advantech WebAccess service, or check if the WebAccess web server (port 80/443) is listeningAffected if The WebAccess service is running and the version cannot be confirmed as V8.2_20170817 or later
-
Confirm web interface accessibilityAccess the WebAccess login page (typically http://localhost/Advantech or the configured hostname) and check the footer or version information displayed on the pageAffected if The web interface is accessible and shows a version prior to 8.2_20170817
If Advantech WebAccess is installed and the version is confirmed to be less than V8.2_20170817, the environment is affected by this 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 data8.2_20170817
Upgrade Advantech WebAccess to version V8.2_20170817 or later to address the untrusted pointer dereference vulnerability. If immediate patching is not possible, restrict network access to the WebAccess server and monitor for indicators of compromise.
- 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-12719 — 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-12719 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