dbcve.org
UagatewayApplication · Unified Automation

CVE-2023-32170

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 →
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
Unified Automation UaGateway OPC UA Server Improper Input Validation Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Unified Automation UaGateway. User interaction is required to exploit this vulnerability in that the target must choose to accept a client certificate. The specific flaw exists within the processing of client certificates. The issue results from the lack of proper validation of certificate data. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-20494.

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

This is an improper input validation vulnerability in Unified Automation UaGateway's OPC UA Server. The flaw exists in the processing of client certificates, where the application fails to properly validate certificate data before handling it. A remote attacker can exploit this by providing a specially crafted client certificate that, when accepted by a user, triggers a denial-of-service condition.

MitigationImplement proper validation and sanitization of all client certificate data before processing. This includes validating certificate structure, fields, and data integrity. Consider applying any available vendor patches for UaGateway.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Check if UaGateway is installed
    Look for UaGateway installation in typical paths: C:\Program Files\Unified Automation\UaGateway\ or C:\Program Files (x86)\Unified Automation\UaGateway\. Check Windows Services for 'UaGateway' service.
    Affected if UaGateway software is present on the system
  2. Determine installed UaGateway version
    Check the version of uagateway.exe in the installation directory by right-clicking the file, selecting Properties, and viewing the Details tab. Alternatively, check the application's About dialog if accessible.
    Affected if The installed version is lower than 1.5.13.487
  3. Verify OPC UA Server is configured
    Open UaGateway configuration and check if an OPC UA Server endpoint is configured and enabled. Look for Server Endpoints in the configuration interface.
    Affected if An OPC UA Server endpoint is configured and listening for client connections
  4. Check certificate handling configuration
    Examine UaGateway settings for client certificate acceptance policy. Look for options controlling whether client certificates are required, optional, or rejected.
    Affected if The OPC UA Server is configured to accept client certificates (not set to reject all)
  5. Confirm user certificate acceptance capability
    Verify that the certificate validation workflow includes user interaction for accepting certificates. Check if manual certificate approval is enabled in the security settings.
    Affected if Users can manually accept or trust client certificates during connection attempts

You are affected if UaGateway version is below 1.5.13.487 AND the OPC UA Server is configured to accept client certificates with user-mediated acceptance enabled.

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

Implement proper validation and sanitization of all client certificate data before processing. This includes validating certificate structure, fields, and data integrity. Consider applying any available vendor patches for UaGateway.

Recommended fix High confidence

1.5.13.487 or later

  1. 1. Navigate to the Unified Automation download page at documentation.unified-automation.com
  2. 2. Locate and download version 1.5.13.487 or later of UaGateway
  3. 3. Back up the current UaGateway configuration files
  4. 4. Stop the UaGateway service
  5. 5. Install the new version (1.5.13.487 or later)
  6. 6. Restore the configuration files if needed
  7. 7. Start the UaGateway service and verify it is running

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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