dbcve.org
OpcApplication · Softing

CVE-2022-39823

HIGH · 7.5 CVSS v3.1 Published 2022-10-20
Fix available
A fix is available. Upgrade to after 6.00 or later.
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
An issue was discovered in Softing OPC UA C++ SDK 5.66 through 6.x before 6.10. An OPC/UA browse request exceeding the server limit on continuation points may cause a use-after-free error

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 Softing OPC UA C++ SDK versions 5.66 through 6.x before 6.10. When an OPC/UA browse request exceeds the server's configured limit on continuation points, the server may attempt to access memory that has already been freed, leading to potential code execution or denial of service.

MitigationUpgrade to Softing OPC UA C++ SDK version 6.10 or later. If immediate upgrading is not feasible, implement request rate limiting on OPC/UA browse operations to prevent clients from sending requests that exceed the continuation point limit.

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
OpcApplication
Affected:>= 5.20, <= 5.22
Opc Ua C\+\+ Software Development KitApplication
Affected:>= 5.70, <= 6.00

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 Softing OPC UA installation
    Locate Softing Opc or Softing OPC UA C++ SDK components on the system, typically installed in program directories or as part of OPC UA server deployments
    Affected if Softing OPC UA software is present on the system
  2. Determine installed version
    Check version information for the installed Softing Opc (versions 5.20-5.22) or Softing OPC UA C++ SDK (versions 5.70-6.00) using product-specific commands, file properties, or configuration tools
    Affected if Installed version falls within >= 5.20 to <= 5.22 for Softing Opc, or >= 5.70 to <= 6.00 for the C++ SDK
  3. Verify OPC UA server is running
    Confirm that an OPC UA server built on the affected Softing SDK is currently active and accepting client connections
    Affected if An OPC UA server instance is running using the vulnerable SDK version
  4. Check continuation point configuration
    Inspect server configuration files or settings related to browse continuation point limits if accessible
    Affected if Continuation point limits are configured and browse requests can exceed those limits

The environment is affected if Softing Opc (5.20-5.22) or Softing OPC UA C++ SDK (5.70-6.00) is installed and an OPC UA server using the SDK is running with configurable continuation point limits that client requests can exceed.

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 a release after 6.00
Interim mitigation

Upgrade to Softing OPC UA C++ SDK version 6.10 or later. If immediate upgrading is not feasible, implement request rate limiting on OPC/UA browse operations to prevent clients from sending requests that exceed the continuation point limit.

Recommended fix High confidence

Softing OPC UA C++ SDK 6.10 or later

  1. 1. Identify the currently installed version of Softing OPC UA C++ SDK by checking project dependencies or build configuration
  2. 2. Confirm the version falls within the affected range: 5.66 through 6.x before 6.10 (or the listed Opc 5.20-5.22 and Opc Ua C++ SDK 5.70-6.00 ranges)
  3. 3. Obtain the fixed release (version 6.10 or later) from the official Softing download channels at industrial.softing.com or www.softing.com
  4. 4. Review the release notes for version 6.10 to understand any API changes or migration requirements
  5. 5. Update the dependency in your project configuration (e.g., CMake, package manager, or build system) to specify version 6.10 or higher
  6. 6. Rebuild and test the application to ensure compatibility with the new SDK version
Caveat Check Softing release notes for version 6.10 for any API changes, breaking changes, or migration steps required from earlier versions

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

Fix this in Opc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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