dbcve.org
UagatewayApplication · Unified Automation

CVE-2023-32174

CRITICAL · 9.1 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.5.14.495 or later.
See remediation →
97/100
Remediation priority · Urgent
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 NodeManagerOpcUa Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code 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 handling of NodeManagerOpcUa objects. 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 execute code in the context of SYSTEM. . Was ZDI-CAN-20577.

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

A Use-After-Free vulnerability in Unified Automation UaGateway's NodeManagerOpcUa component allows remote authenticated attackers to execute arbitrary code in SYSTEM context. The flaw stems from the lack of validating object existence before operating on it, leading to a UAF condition that can be triggered to achieve code execution.

MitigationApply the vendor patch from Unified Automation when available. In the interim, restrict network access to the UaGateway service and enforce strong authentication to reduce attack surface.

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

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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. Confirm UaGateway installation
    Check for UaGateway installation directories, services, or application binaries on the system. Look for processes named 'UaGateway' or 'uagateway' running on the system.
    Affected if UaGateway is installed and running on the system
  2. Determine installed version
    Locate the UaGateway version information in the product's about dialog, installation directory, or by querying the service through its administrative interface if available.
    Affected if Installed version is below 1.5.14.495
  3. Identify NodeManagerOpcUa component usage
    Review UaGateway configuration files or the service management console to determine if the NodeManagerOpcUa component is enabled or actively handling OPC UA client connections.
    Affected if NodeManagerOpcUa is enabled and processing OPC UA requests
  4. Check service context
    Verify the account running the UaGateway Windows service in Services.msc or via 'sc qc' command.
    Affected if Service runs as SYSTEM or an account with elevated privileges
  5. Assess network exposure
    Determine if the UaGateway OPC UA endpoint is accessible from untrusted network segments by reviewing firewall rules and listening ports.
    Affected if Service is exposed to untrusted networks without authentication barriers

User is affected if UaGateway version is below 1.5.14.495 and the NodeManagerOpcUa component is actively handling OPC UA connections.

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 the vendor patch from Unified Automation when available. In the interim, restrict network access to the UaGateway service and enforce strong authentication to reduce attack surface.

Recommended fix High confidence

Unified Automation UaGateway version 1.5.14.495 or later

  1. 1. Obtain the latest version of Unified Automation UaGateway (version 1.5.14.495 or later) from the official vendor website or your authorized distribution channel
  2. 2. Ensure you have a complete backup of the current UaGateway configuration
  3. 3. Stop the UaGateway service
  4. 4. Install the updated version (1.5.14.495 or later) following the vendor's standard installation procedures
  5. 5. Restore the configuration from the backup if needed
  6. 6. Start the UaGateway service and verify it is running correctly
  7. 7. Validate that the NodeManagerOpcUa functionality is operating as expected

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

Fix this in Uagateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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