Pb610 Panel Builder 600Application · Abb

CVE-2019-18994

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to after 2.8.0.424 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Due to a lack of file length check, the HMIStudio component of ABB PB610 Panel Builder 600 versions 2.8.0.424 and earlier crashes when trying to load an empty *.JPR application file. An attacker with access to the file system might be able to cause application malfunction such as denial of service.

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 confidence

A file validation vulnerability exists in HMIStudio component of ABB PB610 Panel Builder 600. When loading an empty *.JPR application file, the lack of file length validation causes the application to crash. An attacker with file system access can exploit this by placing an empty JPR file to trigger a denial of service condition.

MitigationApply vendor-supplied patch for ABB PB610 Panel Builder 600. Restrict file system access to prevent unauthorized placement of malicious JPR files. Only load JPR application files from trusted sources.

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
Pb610 Panel Builder 600Application
Affected:<= 2.8.0.424

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if ABB PB610 Panel Builder 600 is installed
    Search for the product in your system using your operating system's program list or by searching for 'Panel Builder 600' or 'ABB' in your installed applications
    Affected if The product is found on the system
  2. Determine the installed version of ABB PB610 Panel Builder 600
    Right-click on the application executable or access the program's About/Help section to view version information, then compare it to the affected range: version 2.8.0.424 or lower
    Affected if The installed version is 2.8.0.424 or any version lower than 2.8.0.424
  3. Locate JPR application files on the system
    Search your file system for files with the .JPR extension, particularly in project directories or application data folders related to ABB Panel Builder 600
    Affected if JPR files are present on the system and could be accessed by unauthorized users
  4. Check for application crash reports or logs
    Examine Windows Event Viewer for application crash events, or check for crash dump files in the application directory or user documents folders
    Affected if Recent crash events related to HMIStudio or Panel Builder 600 are logged after loading JPR files
  5. Verify file system access controls on JPR file locations
    Review file permissions on directories containing JPR files to determine if untrusted users could place files in those locations
    Affected if Users without proper authorization can write to directories where JPR files are stored

You are affected if ABB PB610 Panel Builder 600 version 2.8.0.424 or lower is installed and JPR files exist in accessible locations on your system.

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 a release after 2.8.0.424
Interim mitigation

Apply vendor-supplied patch for ABB PB610 Panel Builder 600. Restrict file system access to prevent unauthorized placement of malicious JPR files. Only load JPR application files from trusted sources.

Fix this in Pb610 Panel Builder 600 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18994 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18994 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