dbcve.org
UagatewayApplication · Unified Automation

CVE-2023-32172

MEDIUM · 6.5 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.5.13.487 or later.
See remediation →
71/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 OPC UA Server Use-After-Free 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. The specific flaw exists within the implementation of the ImportXML function. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-20497.

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 use-after-free vulnerability exists in Unified Automation UaGateway's OPC UA server within the ImportXML function. The flaw results from insufficient validation of object existence before performing operations on the object, allowing an authenticated attacker to cause a denial-of-service condition.

MitigationApply the vendor-provided patch or update to a fixed version of Unified Automation UaGateway. If no patch is available, implement network segmentation and restrict access to the OPC UA server to authenticated, authorized personnel only.

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

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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. Verify UaGateway installation and version
    Locate the UaGateway installation directory and check the version information (typically in the product's about dialog, version file, or executable properties). Compare the version number to the affected range: versions prior to 1.5.13.487 are vulnerable.
    Affected if The installed version is Unified Automation UaGateway and the version is less than 1.5.13.487
  2. Confirm OPC UA server is enabled
    Inspect the UaGateway configuration to determine if an OPC UA server is configured and running. This is typically found in the gateway configuration file or management interface.
    Affected if An OPC UA server is actively configured and listening for connections
  3. Check ImportXML function accessibility
    Verify that the ImportXML functionality is available in the deployed OPC UA server. This function allows importing XML configuration files into the UA server namespace.
    Affected if The ImportXML function is accessible to authenticated users or applications
  4. Assess OPC UA server network exposure
    Determine the network binding and access controls for the OPC UA server. Check if the server is bound to accessible network interfaces and what authentication/authorization mechanisms are in place.
    Affected if The OPC UA server is accessible to network entities without proper access restrictions or uses weak authentication

You are affected if Unified Automation UaGateway version is less than 1.5.13.487 and an OPC UA server with the ImportXML function is enabled and accessible to authenticated attackers.

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.13.487 or later
Fixed in 1.5.13.487
Interim mitigation

Apply the vendor-provided patch or update to a fixed version of Unified Automation UaGateway. If no patch is available, implement network segmentation and restrict access to the OPC UA server to authenticated, authorized personnel only.

Recommended fix Moderate confidence

UaGateway version 1.5.13.487 or later

  1. 1. Identify the current installed version of Unified Automation UaGateway by checking the application or system information
  2. 2. Navigate to the official Unified Automation website or their documentation portal at documentation.unified-automation.com
  3. 3. Locate and download UaGateway version 1.5.13.487 or a later stable release
  4. 4. Before upgrading, backup any existing configuration files and data for the UaGateway installation
  5. 5. Stop the UaGateway service if it is currently running
  6. 6. Install the upgraded version (1.5.13.487 or later) following the vendor's installation instructions
  7. 7. After installation, restore the backed-up configuration if needed
  8. 8. Start the UaGateway service and verify it is running correctly

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

Fix this in Uagateway Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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