dbcve.org
Saia Pg5 Controls SuiteApplication · Honeywell

CVE-2023-51605

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-18644.

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 XML External Entity (XXE) vulnerability in Honeywell Saia PG5 Controls Suite's XML parser. The application fails to properly restrict XXE references when parsing XML files, allowing attackers to craft malicious XML documents containing external entity references that cause the parser to access arbitrary URIs and embed the retrieved contents back into the XML document for further processing, leading to information disclosure.

MitigationDisable XML external entity (XXE) processing in the application's XML parser configuration, or implement strict input validation to reject XML documents containing DOCTYPE declarations with external entity references.

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 is installed
    Locate the Saia PG5 installation directory, typically under Program Files or a custom install path, and verify the presence of PG5 core executables and libraries.
    Affected if The software is present and operational in the environment.
  2. Identify the installed version
    Check the application executable or DLL file properties for version information, or look for a version file in the installation directory.
    Affected if Any version of Saia PG5 Controls Suite is installed, as all versions are affected.
  3. Locate XML parser configuration files
    Search the installation directory for configuration files related to XML processing, such as settings files, config.xml, or parser-related XML configuration files.
    Affected if The application uses an XML configuration or processes XML files.
  4. Check XML parser XXE settings
    Inspect XML parser configuration files for settings that control external entity processing, such as flags or properties named 'external-entities', 'xxe', 'disable-xxe', or similar.
    Affected if XXE processing is not explicitly disabled in the parser configuration.
  5. Verify XML file processing functionality
    If the application imports or processes XML-based project files, configuration files, or data exchange files, confirm this functionality is in use.
    Affected if The application actively parses XML files, enabling the XXE attack surface.

If Saia PG5 Controls Suite is installed and processes XML files without XXE protection explicitly configured, the environment is affected by this vulnerability.

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 XML external entity (XXE) processing in the application's XML parser configuration, or implement strict input validation to reject XML documents containing DOCTYPE declarations with external entity references.

Fix this in Saia Pg5 Controls Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51605 — 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-51605 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