CVE-2019-18996
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 · uneditedPath settings in HMIStudio component of ABB PB610 Panel Builder 600 versions 2.8.0.424 and earlier accept DLLs outside of the program directory, potentially allowing an attacker with access to the local file system the execution of code in the application’s context.
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 confidenceThe HMIStudio component in ABB PB610 Panel Builder 600 versions 2.8.0.424 and earlier has insecure DLL loading due to path settings that accept DLLs from outside the program directory. An attacker with local file system access can place a malicious DLL in a location from which the application will load it, resulting in arbitrary code execution in the application's context.
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.8.0.424CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ABB PB610 Panel Builder 600 installationOpen Windows Control Panel > Programs and Features, or check the installation directory for HMIStudio or Panel Builder 600 executablesAffected if The software is installed on the system
-
Determine installed versionRight-click the main Panel Builder executable (typically PanelBuilder600.exe or similar), select Properties, and check the File Version field in the Details tabAffected if The reported version is 2.8.0.424 or earlier
-
Locate HMIStudio componentSearch for HMIStudio.exe or related DLLs in the installation directory and common application data foldersAffected if HMIStudio executable or its DLLs are present on the system
-
Check for unauthorized DLL placement opportunitiesReview folder permissions on directories from which the application may load DLLs, including the application directory, system paths, and user-writable locationsAffected if Non-privileged users can write to directories in the application's DLL search path (other than the program directory)
-
Verify DLL loading behaviorUse Process Monitor or similar tool to observe DLL load attempts when launching HMIStudio, checking for loads from paths outside the program directoryAffected if The application loads DLLs from directories outside its installed folder
A user is affected if ABB PB610 Panel Builder 600 version 2.8.0.424 or earlier is installed and the HMIStudio component can load DLLs from locations outside the program 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 dataUpgrade to a patched version of ABB PB610 Panel Builder 600. Additionally, restrict file system access to prevent unauthorized users from placing DLLs in locations from which the application loads libraries.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18996 — 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-18996 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