CVE-2019-16899
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 · uneditedIn Advantech WebAccess/HMI Designer 2.1.9.31, Data from a Faulting Address controls Code Flow starting at PM_V3!CTagInfoThreadBase::GetNICInfo+0x0000000000512918.
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 control flow hijack vulnerability exists in Advantech WebAccess/HMI Designer 2.1.9.31 where data from an attacker-controlled memory address (faulting address) influences code execution flow in the PM_V3!CTagInfoThreadBase::GetNICInfo function. This indicates a memory corruption issue allowing potential 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.
-
Locate WebAccess/HMI Designer installation directoryCheck common installation paths such as C:\Program Files\Advantech\WebAccess\HMI Designer or C:\Advantech\WebAccess\HMI Designer. Use file explorer or command: dir /s /b "PM_V3.dll" 2>nulAffected if The product is not installed or the PM_V3.dll component is not found in expected directories
-
Verify the installed version numberLocate the version information for HMI Designer. Right-click the executable (typically HMIDesigner.exe in the installation folder), select Properties, and check the File Version or Product Version field. Alternatively, use PowerShell: Get-ItemProperty "C:\Program Files\Advantech\WebAccess\HMI Designer\HMIDesigner.exe" | Select-Object VersionInfoAffected if The Product Version or File Version shows exactly 2.1.9.31
-
Confirm the vulnerable PM_V3.dll component versionNavigate to the PM_V3.dll file in the installation folder (commonly in bin or runtime subdirectory), right-click and view Properties, or run: powershell (Get-Item "path\to\PM_V3.dll").VersionInfoAffected if PM_V3.dll version matches 2.1.9.31 or is listed as version 2.1.9.31 specifically
-
Check if HMI Designer service or runtime is actively runningOpen Task Manager or use command: tasklist | findstr -i "HMI Designer" or check services.msc for WebAccess/HMI Designer related servicesAffected if The HMI Designer application or its runtime components are currently executing on the system
The system is affected if Advantech WebAccess/HMI Designer version 2.1.9.31 is installed, particularly if the PM_V3.dll component at version 2.1.9.31 is present and the application is in use.
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 vendor-supplied patches when available. Until then, restrict network access to the HMI Designer system and implement network segmentation to limit exposure of this industrial control system component.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16899 — 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-16899 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