dbcve.org
Saia Pg5 Controls SuiteApplication · Honeywell

CVE-2023-51600

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Honeywell Saia PG5 Controls Suite. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of XML files. Due to the improper restriction of XML External Entity (XXE) references, a crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this vulnerability to disclose information in the context of the current process. . Was ZDI-CAN-18456.

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 · high confidence

This is an XXE (XML External Entity) injection vulnerability in Honeywell Saia PG5 Controls Suite's XML parser. The application fails to properly restrict XML external entity references, allowing an attacker to craft malicious XML documents that reference external URIs. When parsed, the application will access these URIs and embed the contents back into the XML document, enabling information disclosure in the context of the current process.

MitigationDisable external entity processing in the XML parser configuration or use a secure XML parser that has XXE protection enabled by default. Validate and sanitize all XML input before processing.

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
Saia Pg5 Controls SuiteApplication
Affected:all versions= 2.3.193

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Confirm Saia PG5 Controls Suite installation
    Look for Saia PG5 installation directory, typically under C:\Program Files\Honeywell\Saia PG5 or C:\Saia-PG5. Check Program Files for Saia PG5 folder.
    Affected if Saia PG5 Controls Suite is installed on the system
  2. Identify installed version
    Check the version of the installed Saia PG5 software. Look in the installation directory for version information, or check Windows Programs and Features for the version number.
    Affected if Version is 2.3.193 or below, or version cannot be determined (all versions are affected)
  3. Identify XML parsing usage
    Search the Saia PG5 installation and project directories for XML files (.xml), XLS, or other file formats processed by the application. Check for XML import/export features in the software.
    Affected if Application processes XML files or uses XML-based project files
  4. Check XML parser external entity configuration
    Examine Saia PG5 configuration files, registry entries, or XML parser settings for XXE/external entity processing settings. Look in the installation folder for config files that control XML parsing behavior.
    Affected if XML parser allows external entity references or no XXE protection is configured

A user is affected if Saia PG5 Controls Suite is installed and the application processes XML input with external entity processing enabled in the parser configuration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable external entity processing in the XML parser configuration or use a secure XML parser that has XXE protection enabled by default. Validate and sanitize all XML input before processing.

Fix this in Saia Pg5 Controls Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-51600 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