CVE-2017-16728
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 8.3. There are multiple vulnerabilities that may allow an attacker to cause the program to use an invalid memory address, resulting in a program crash.
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 8.3 contain an untrusted pointer dereference vulnerability that allows attackers to cause the program to access invalid memory addresses, resulting in denial-of-service via program crash.
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.3CVSS 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.
-
Confirm Advantech WebAccess is installedCheck if Advantech WebAccess software exists on the system by looking in installed programs list (Programs and Features in Control Panel, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' in PowerShell)Affected if Advantech WebAccess or WebAccess is listed in installed programs
-
Identify installed WebAccess versionLocate the WebAccess installation directory or executable files and check version information. Common locations include C:\Advantech\WebAccess or C:\Program Files\Advantech\WebAccess. Right-click on the main executable (often named something like BwOpcRpt.exe, BwMGR.exe, or similar) and select Properties > Details to view the File VersionAffected if Cannot determine version or version is not displayed
-
Compare version against affected rangeCompare the identified version number to the affected range. WebAccess versions prior to 8.3 are vulnerable. If the version shown is 8.3 or later (for example 8.3.0, 8.3.1), the system is not affected by this specific CVEAffected if Installed version is a number less than 8.3 (such as 8.2, 8.1, 8.0, or earlier)
-
Verify WebAccess services are runningOpen Services (services.msc) and check if WebAccess-related services are running, or use command 'Get-Service | Where-Object {$_.DisplayName -like "*WebAccess*"}' in PowerShellAffected if WebAccess services are actively running and version is less than 8.3
A system is affected if Advantech WebAccess is installed with a version number lower than 8.3 and the software or its services are actively present on the machine.
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.3
Upgrade to Advantech WebAccess version 8.3 or later to obtain the vendor patch for this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16728 — 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-16728 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