CVE-2019-16900
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 · uneditedAdvantech WebAccess/HMI Designer 2.1.9.31 has a User Mode Write AV starting at MSVCR90!memcpy+0x000000000000015c.
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 confidenceAdvantech WebAccess/HMI Designer 2.1.9.31 contains a memory corruption vulnerability in the MSVCR90.dll memcpy function, resulting in a User Mode Write Access Violation. This indicates a buffer overflow or out-of-bounds write condition that could allow an attacker to overwrite arbitrary memory locations, potentially leading to arbitrary code execution.
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= 2.1.9.31CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify Advantech WebAccess/HMI Designer installationCheck for the presence of the WebAccess/HMI Designer installation directory, typically found under C:\Program Files\Advantech\WebAccess HMI Designer or C:\Program Files (x86)\Advantech\WebAccess HMI DesignerAffected if The software is not installed or the directory does not exist, then the system is not affected by this specific CVE
-
Check installed version of WebAccess/HMI DesignerLocate the executable file (typically HmiDesigner.exe) and check its version property, or look in the software's About/Help section for the exact version numberAffected if The installed version is exactly 2.1.9.31, indicating the system is running the affected version
-
Verify presence of MSVCR90.dll in installationCheck for the MSVCR90.dll file within the WebAccess/HMI Designer installation folder or subdirectories, particularly in the bin or runtime foldersAffected if The vulnerable MSVCR90.dll is present in the installation directory and the software version is 2.1.9.31
A system is affected by CVE-2019-16900 only if Advantech WebAccess/HMI Designer version 2.1.9.31 is installed and the MSVCR90.dll library is present in the installation directory.
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.
From vendor dataApply any available vendor patches or upgrade to a newer version of Advantech WebAccess/HMI Designer. If no patch exists, implement network segmentation and restrict access to the HMI Designer to trusted personnel only.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16900 — 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-2019-16900 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