dbcve.org
WebaccessApplication · Advantech

CVE-2019-10993

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-28
Fix available
A fix is available. Upgrade to after 8.3.5 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
In WebAccess/SCADA Versions 8.3.5 and prior, multiple untrusted pointer dereference vulnerabilities may allow a remote attacker to execute arbitrary code.

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

WebAccess/SCADA versions 8.3.5 and prior contain multiple untrusted pointer dereference vulnerabilities. These memory corruption issues allow remote attackers to dereference pointers that point to untrusted or invalid memory locations, potentially leading to arbitrary code execution on the affected system.

MitigationUpgrade WebAccess/SCADA to a version beyond 8.3.5 that addresses these vulnerabilities. If upgrades are not immediately possible, isolate the SCADA system from untrusted networks and implement compensating controls such as network segmentation and strict access controls.

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.5

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.1/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. Identify installed WebAccess/SCADA version
    Check Windows registry under HKLM\SOFTWARE\Advantech\WebAccess\Version or look for version info in the installation directory (commonly C:\Advantech\WebAccess)
    Affected if Version displayed is 8.3.5 or lower, or if no version is found but Advantech WebAccess software is present on the system
  2. Verify WebAccess services are running
    Open Windows Services console (services.msc) and look for 'Advantech WebAccess' or 'WebAccess' services, or run 'net start' command to list running services
    Affected if WebAccess-related services are running, indicating the software is active and potentially exposed
  3. Check network exposure of web interface
    Run 'netstat -an | findstr LISTENING' to identify listening ports (typically 80, 443, or 8080) and check if the service is bound to 0.0.0.0 or external interfaces rather than localhost only
    Affected if The web interface ports are listening on external network interfaces accessible from untrusted networks
  4. Confirm SCADA system is accessible remotely
    Review firewall rules or network configuration to determine if the WebAccess web server port is open to untrusted network segments or the internet
    Affected if Firewall rules allow external access to WebAccess ports from untrusted networks or the internet

A system is affected if it runs Advantech WebAccess/SCADA version 8.3.5 or lower and has the web interface network-accessible, since the untrusted pointer dereference vulnerabilities can be exploited remotely.

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.

From vendor data
Upgrade available Upgrade to a release after 8.3.5
Interim mitigation

Upgrade WebAccess/SCADA to a version beyond 8.3.5 that addresses these vulnerabilities. If upgrades are not immediately possible, isolate the SCADA system from untrusted networks and implement compensating controls such as network segmentation and strict access controls.

Fix this in Webaccess Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10993 — 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-2019-10993 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