dbcve.org
UagatewayApplication · Unified Automation

CVE-2023-32173

MEDIUM · 5.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.5.14.495 or later.
See remediation →
64/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Unified Automation UaGateway AddServer XML Injection Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Unified Automation UaGateway. Authentication is required to exploit this vulnerability when the product is in its default configuration. The specific flaw exists within the implementation of the AddServer method. By specifying crafted arguments, an attacker can cause invalid characters to be inserted into an XML configuration file. An attacker can leverage this vulnerability to create a persistent denial-of-service condition on the system. . Was ZDI-CAN-20576.

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

Unified Automation UaGateway contains an XML injection vulnerability in the AddServer method. An authenticated attacker can supply crafted arguments containing invalid characters that get written to an XML configuration file, causing a persistent denial-of-service condition where the service becomes unavailable or non-functional.

MitigationApply vendor-supplied patches when available. Until then, restrict administrative access to the AddServer functionality, enforce strict input validation on server parameters, and consider network segmentation to limit exposure to authenticated attackers.

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
UagatewayApplication
Affected:< 1.5.14.495

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/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 installed UaGateway version
    Determine the currently installed version of Unified Automation UaGateway (typically available in the application itself, its installer details, or Windows Programs and Features)
    Affected if The installed version is lower than 1.5.14.495
  2. Verify AddServer method accessibility
    Confirm whether the AddServer administrative function is exposed and accessible to authenticated users in your deployment
    Affected if AddServer method is accessible to authenticated users without additional restrictive access controls
  3. Inspect XML configuration files
    Examine the XML configuration files used by UaGateway for any server entries containing unexpected characters, malformed XML structure, or suspicious content in server parameters
    Affected if XML configuration files contain entries with invalid characters or malformed XML that could result from injection
  4. Check service availability
    Verify whether the UaGateway service is running normally and responding to requests
    Affected if Service is unavailable, non-functional, or exhibiting denial-of-service behavior

Environment is affected if UaGateway version is below 1.5.14.495 and the AddServer method is accessible to authenticated users, with possible confirmation through malformed XML in configuration files or service disruption

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.

dbcve · scoped
Upgrade available Upgrade to 1.5.14.495 or later
Fixed in 1.5.14.495
Interim mitigation

Apply vendor-supplied patches when available. Until then, restrict administrative access to the AddServer functionality, enforce strict input validation on server parameters, and consider network segmentation to limit exposure to authenticated attackers.

Recommended fix High confidence

1.5.14.495 or later

  1. 1. Back up the current UaGateway configuration files and installation directory.
  2. 2. Download the updated UaGateway version 1.5.14.495 or later from the official Unified Automation website (documentation.unified-automation.com).
  3. 3. Stop the UaGateway service to ensure no active connections during the upgrade.
  4. 4. Install the updated version (1.5.14.495 or later) following the vendor's standard installation procedures.
  5. 5. Restore the backed-up configuration files if the upgrade does not preserve them automatically.
  6. 6. Start the UaGateway service and verify that the AddServer method functions correctly without XML injection issues.
  7. 7. Validate that the XML configuration files are being written with proper character encoding and do not contain invalid characters.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uagateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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