dbcve.org
Opc Ua C\+\+ Demo ServerApplication · Unified Automation

CVE-2022-37012

HIGH · 7.5 CVSS v3.1 Published 2023-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Unified Automation OPC UA C++ Demo Server 1.7.6-537. Authentication is not required to exploit this vulnerability. The specific flaw exists within the OpcUa_SecureListener_ProcessSessionCallRequest method. A crafted OPC UA message can force the server to incorrectly update a reference count. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-16927.

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 a memory management vulnerability in the Unified Automation OPC UA C++ Demo Server. The OpcUa_SecureListener_ProcessSessionCallRequest method incorrectly updates a reference count when processing specially crafted OPC UA messages, allowing an unauthenticated remote attacker to cause a denial of service by corrupting memory through improper reference counting.

MitigationIf an official patch is available from Unified Automation, apply it promptly. Otherwise, network-segment the affected server or restrict access to trusted clients only, as exploitation requires no authentication.

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
Opc Ua C\+\+ Demo ServerApplication
Affected:= 1.7.6.537

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Unified Automation OPC UA C++ Demo Server is installed
    Locate the server executable or check installed programs. Common locations: C:\Program Files\Unified Automation\ or /opt/unified-automation/. On Windows, check Add/Remove Programs. On Linux, check package manager or /usr/local/ua.
    Affected if The software is present on the system and matches the affected product name.
  2. Determine the installed version
    Check the version of the Demo Server binary. Right-click the executable and select Properties > Details, or run the server with a version flag like --version or -v if available. Check README or version files in the installation directory.
    Affected if The version is exactly 1.7.6.537.
  3. Verify the server is network-accessible
    Check if the OPC UA server process is listening on a network port (commonly OPC UA default ports like 4840, or configured ports). Use netstat -an | findstr 4840 or similar commands, or check the server configuration file for enabled network endpoints.
    Affected if The server is exposed to network access without proper firewall or access controls.
  4. Confirm the vulnerable method is in use
    The flaw is in OpcUa_SecureListener_ProcessSessionCallRequest which handles session call requests. If the server accepts OPC UA session calls from clients, this code path is exercised. Check server logs or monitoring for active session activity.
    Affected if The server accepts and processes OPC UA session call requests from clients.

A user is affected if the Unified Automation OPC UA C++ Demo Server version 1.7.6.537 is installed and the server is accessible over the network to process OPC UA messages.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If an official patch is available from Unified Automation, apply it promptly. Otherwise, network-segment the affected server or restrict access to trusted clients only, as exploitation requires no authentication.

Recommended fix Moderate confidence

Latest available version of Unified Automation OPC UA C++ Demo Server (version higher than 1.7.6-537)

  1. 1. Visit the Unified Automation website (documentation.unified-automation.com) or contact their support to obtain the latest version of the OPC UA C++ Demo Server.
  2. 2. Download the most recent stable release that supersedes version 1.7.6-537.
  3. 3. Stop the currently running Demo Server instance.
  4. 4. Back up any existing configuration files, certificates, and application data.
  5. 5. Install the new version following the vendor's installation instructions.
  6. 6. Restore the backed-up configuration and certificates to the new installation.
  7. 7. Start the updated Demo Server and verify normal operation.
  8. 8. Test that the vulnerability is no longer reproducible with the updated version.
Caveat Review release notes for any changes in configuration format, deprecated features, or API differences between 1.7.6-537 and the target version.

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

Fix this in Opc Ua C\+\+ Demo Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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