dbcve.org
WebaccessApplication · Advantech

CVE-2018-10590

HIGH · 7.5 CVSS v3.0 Published 2018-05-15
Fix available
A fix is available. Upgrade to 8.3.1 or later.
See remediation →
84/100
Remediation priority · High
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, an information exposure vulnerability through directory listing has been identified, which may allow an attacker to find important files that are not normally visible.

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

Advantech WebAccess SCADA software contains an information disclosure vulnerability where directory listing is enabled on the web server, allowing unauthenticated attackers to enumerate files and directories that should not be publicly accessible. This can reveal configuration files, credentials, or other sensitive system information.

MitigationDisable directory listing in the web server configuration (IIS/Apache) and apply vendor patches for the specific affected versions. Restrict access to sensitive files via proper 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.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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Advantech WebAccess installation and version
    Locate the WebAccess installation directory, typically under C:\Advantech\WebAccess or C:\Inetpub\wwwroot\WAD. Check for version information in the about dialog, README files, or installation logs. Compare the found version against the affected ranges: WebAccess <= 8.2_20170817, <= 8.3.0, or < 8.3.1; Dashboard <= 2.0.15; Webaccess/nms <= 2.0.3.
    Affected if The installed version is any of 8.2_20170817 or earlier, 8.3.0 or earlier, or below 8.3.1 for WebAccess SCADA; Dashboard version 2.0.15 or earlier; or Webaccess/nms 2.0.3 or earlier.
  2. Identify the web server component
    Determine whether the system uses IIS or another web server for hosting WebAccess. Check the Windows Services list for IIS Admin Service or examine the web server configuration files in the WebAccess installation directory.
    Affected if IIS or Apache is configured to serve the WebAccess web application.
  3. Verify directory listing is enabled
    Check the web server configuration (IIS Manager under Directory Browsing, or httpd.conf/htaccess for Apache) to see if directory listing is permitted. Alternatively, attempt to access a known directory path such as /webaccess/ or the root web directory without an index file to see if a directory listing is returned.
    Affected if Directory listing is enabled on any web directory under the WebAccess application path.
  4. Test for sensitive file exposure
    Attempt to access common paths that may reveal sensitive information, such as configuration directories, backup folders, or log directories within the WebAccess web root. Examples include paths like /scada/, /config/, /backup/, or parent directories. Observe if a full directory listing is returned showing file contents.
    Affected if Directory listing is returned and reveals configuration files, credentials, or other sensitive system files that should not be publicly accessible.

A system is affected if it runs any of the listed Advantech WebAccess versions AND the web server has directory listing enabled, allowing unauthenticated enumeration of files and directories.

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

Disable directory listing in the web server configuration (IIS/Apache) and apply vendor patches for the specific affected versions. Restrict access to sensitive files via proper access controls.

Fix this in Webaccess Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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