dbcve.org
WebaccessApplication · Advantech

CVE-2017-16724

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-05
Fix available
A fix is available. Upgrade to 8.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A Stack-based Buffer Overflow issue was discovered in Advantech WebAccess versions prior to 8.3. There are multiple instances of a vulnerability that allows too much data to be written to a location on the stack.

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 confidence

Stack-based buffer overflow vulnerability in Advantech WebAccess versions prior to 8.3. Multiple locations in the software allow writing more data than allocated on the stack, which can overwrite return addresses and other stack frames, potentially enabling remote code execution.

MitigationUpgrade to Advantech WebAccess version 8.3 or later. If immediate patching is not possible, isolate the affected systems via network segmentation and monitor for exploitation attempts.

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
WebaccessApplication
Affected:< 8.3

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Advantech WebAccess installation
    Check for WebAccess installation in default locations: C:\Program Files\Advantech\WebAccess or C:\Program Files (x86)\Advantech\WebAccess. Also check Windows Registry under HKLM\SOFTWARE\Advantech\WebAccess or HKLM\SOFTWARE\WOW6432Node\Advantech\WebAccess for installation path.
    Affected if Advantech WebAccess is not found on the system, the user is not affected by this CVE.
  2. Determine installed WebAccess version
    Locate the version information file (such as version.ini, about.exe, or the main executable) within the WebAccess installation directory. Right-click the main executable, select Properties, and view the Version tab. Alternatively, open a command prompt, navigate to the installation directory, and run: dir /s *.exe to list executables, then use: "executable_name.exe" --version if supported.
    Affected if The installed version is a release prior to 8.3 (for example, 8.2, 8.1, 8.0, or earlier).
  3. Check if WebAccess services are running
    Open Windows Services (services.msc) and look for Advantech WebAccess services such as BroadWeb, WADashboard, WAClient, or similar. Alternatively, run: sc query type= service state= all | findstr /i "WebAccess" in an elevated command prompt.
    Affected if The software is installed at a vulnerable version AND the WebAccess services are running, exposing the vulnerability.
  4. Verify network exposure of WebAccess ports
    Check if the WebAccess web server port (typically TCP 80 or TCP 443 by default) is listening on network interfaces. Run: netstat -an | findstr ":80" or :443. Also review any firewall rules or router port forwarding configurations that may expose these ports.
    Affected if The vulnerable version is installed, services are running, AND the web interface is accessible from the network, indicating potential exposure to remote exploitation.

A user is affected if Advantech WebAccess version 8.3 or later is NOT installed, the software services are active, and the web interface is exposed on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.3 or later
Fixed in 8.3
Interim mitigation

Upgrade to Advantech WebAccess version 8.3 or later. If immediate patching is not possible, isolate the affected systems via network segmentation and monitor for exploitation attempts.

Recommended fix High confidence

Advantech WebAccess 8.3

  1. Identify the current version of Advantech WebAccess installed in the environment
  2. Verify the current version is below 8.3 (any version prior to 8.3 is vulnerable)
  3. Obtain Advantech WebAccess version 8.3 or later from the official vendor
  4. Schedule a maintenance window following organizational change management procedures
  5. Back up the current WebAccess configuration and database
  6. Install WebAccess version 8.3 or the latest stable version available
  7. Verify the upgrade was successful by checking the installed version number
  8. Validate that WebAccess services are running correctly post-upgrade
Caveat Review release notes for version 8.3 to check for any configuration or feature changes that may require adjustment in your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webaccess Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-16724 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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