CVE-2020-10619
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 attacker could use a specially crafted URL to delete files outside the WebAccess/NMS's (versions prior to 3.0.2) control.
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 confidenceA path traversal vulnerability in WebAccess/NMS versions prior to 3.0.2 allows attackers to use specially crafted URLs to delete files outside the application's intended control directory, potentially leading to denial of service or further system compromise.
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< 3.0.2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WebAccess/NMS installationLocate the WebAccess/NMS installation directory or check for the web service process. Common locations include C:\WebAccess\ or /opt/webaccess/ on Linux systems. Look for nms.exe or related service processes.Affected if WebAccess/NMS software is found on the system
-
Identify installed versionCheck the version of WebAccess/NMS. This is typically displayed in the web interface login page, in an about dialog, or in version files within the installation directory. Look for files like version.txt, about.html, or check the Windows service properties.Affected if The installed version cannot be determined or is displayed as a version prior to 3.0.2
-
Compare version against affected rangeReview the identified version number against the affected range: versions prior to 3.0.2. If the version shown is 3.0.1, 2.x, or any version number less than 3.0.2, the installation is within the affected range.Affected if The installed version is any release prior to 3.0.2 (for example, 3.0.1, 3.0.0, 2.x, 1.x)
-
Verify web interface accessibilityDetermine if the WebAccess/NMS web interface is exposed on the network. Check firewall rules, IIS/Apache configuration, or port bindings (typically ports 80, 443, or 8080). The vulnerability is exploitable through HTTP/HTTPS URLs.Affected if The web interface is accessible from network segments where untrusted users could submit crafted URLs
A system is affected if WebAccess/NMS is installed with any version prior to 3.0.2 and the web interface is network-accessible.
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.
dbcve · scoped3.0.2
Upgrade WebAccess/NMS to version 3.0.2 or later to obtain the patch for this vulnerability.
3.0.2
- Verify current WebAccess/NMS version by checking the application interface or system information
- Download WebAccess/NMS version 3.0.2 from the official Advantech vendor source
- Review upgrade documentation provided by Advantech for WebAccess/NMS
- Create a complete backup of the current WebAccess/NMS installation and configuration
- Stop the WebAccess/NMS service before initiating the upgrade
- Install version 3.0.2 following vendor-provided installation procedures
- Verify the upgrade was successful by checking the version number
- Restart the WebAccess/NMS service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10619 — 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-2020-10619 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