dbcve.org
WebaccessApplication · Advantech

CVE-2018-7497

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-15
Fix available
A fix is available. Upgrade to 8.3.1 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 Advantech WebAccess versions V8.2_20170817 and prior, WebAccess versions V8.3.0 and prior, WebAccess Dashboard versions V.2.0.15 and prior, WebAccess Scada Node versions prior to 8.3.1, and WebAccess/NMS 2.0.3 and prior, several untrusted pointer dereference vulnerabilities have been identified, which may allow an 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

Multiple untrusted pointer dereference vulnerabilities in Advantech WebAccess (ICS/SCADA software) allow attackers to manipulate pointers to achieve memory corruption and potentially execute arbitrary code. The vulnerabilities affect WebAccess, WebAccess Dashboard, WebAccess Scada Node, and WebAccess/NMS across multiple version ranges.

MitigationApply vendor patches by upgrading to WebAccess V8.3.1 or later, WebAccess/NMS 2.0.4 or later, and respective patched versions of Dashboard and Scada Node. For ICS environments, test updates in a staging environment before production deployment.

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.2_20170817<= 8.3.0
Webaccess DashboardApplication
Affected:<= 2.0.15
Webaccess ScadaApplication
Affected:< 8.3.1
Webaccess\/nmsApplication
Affected:<= 2.0.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. Identify if Advantech WebAccess products are installed
    Check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'WebAccess' or 'Advantech', or look for installation directories such as C:\Advantech or C:\Program Files\Advantech
    Affected if Any Advantech WebAccess, WebAccess Dashboard, WebAccess Scada, or WebAccess/NMS installation is found on the system
  2. Determine the installed WebAccess version
    Locate the WebAccess installation and check version information in the program files, typically in the main executable or a version file within the Advantech WebAccess directory
    Affected if The version is 8.2_20170817 or earlier, or 8.3.0 or earlier (for WebAccess)
  3. Determine the WebAccess Dashboard version
    Check the installed Dashboard component version through the program directory or registry entry if present
    Affected if The Dashboard version is 2.0.15 or earlier
  4. Determine the WebAccess Scada version
    Locate the Scada Node installation and retrieve its version number from the program files or application properties
    Affected if The Scada version is earlier than 8.3.1 (any version below 8.3.1)
  5. Determine the WebAccess/NMS version
    Check the NMS component installation for its version information
    Affected if The NMS version is 2.0.3 or earlier
  6. Verify the web service is accessible
    Attempt to access the WebAccess web interface on the default ports (typically HTTP port 80 or 8080) to confirm the vulnerable service is exposed
    Affected if The web interface responds and the product version falls within the affected ranges

You are affected if any Advantech WebAccess, WebAccess Dashboard, WebAccess Scada, or WebAccess/NMS product is installed with a version matching or falling below the affected ranges: WebAccess <= 8.2_20170817 or <= 8.3.0, Dashboard <= 2.0.15, Scada < 8.3.1, or NMS <= 2.0.3.

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.1 or later
Fixed in 8.3.1
Interim mitigation

Apply vendor patches by upgrading to WebAccess V8.3.1 or later, WebAccess/NMS 2.0.4 or later, and respective patched versions of Dashboard and Scada Node. For ICS environments, test updates in a staging environment before production deployment.

Recommended fix Moderate confidence

WebAccess Scada: 8.3.1 or later; WebAccess: newer than 8.3.0; WebAccess Dashboard: newer than 2.0.15; WebAccess/NMS: newer than 2.0.3

  1. Identify the specific Advantech WebAccess component running in your environment (WebAccess, WebAccess Dashboard, WebAccess Scada, or WebAccess/NMS)
  2. For WebAccess Scada: Upgrade to version 8.3.1 or later
  3. For WebAccess versions: Upgrade to a version newer than 8.3.0
  4. For WebAccess Dashboard: Upgrade to a version newer than 2.0.15
  5. For WebAccess/NMS: Upgrade to a version newer than 2.0.3
  6. After upgrading, verify the new version number matches the fixed release
  7. Test that the WebAccess application functions normally post-upgrade
Caveat Test application functionality after upgrade as minor version jumps may introduce feature changes

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

Fix this in Webaccess Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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