dbcve.org
OpcApplication · Softing

CVE-2023-41151

HIGH · 7.5 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to after 6.20.1 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 uncaught exception issue discovered in Softing OPC UA C++ SDK before 6.30 for Windows operating system may cause the application to crash when the server wants to send an error packet, while socket is blocked on writing.

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

The Softing OPC UA C++ SDK before version 6.30 has an uncaught exception vulnerability on Windows. When the server attempts to send an error packet while the socket is blocked on a write operation, the exception is not caught, causing the application to crash. This results in a denial of service since any attacker able to trigger an error packet during socket blocking can cause the application to terminate.

MitigationUpgrade to Softing OPC UA C++ SDK version 6.30 or later, which contains the fix for this uncaught exception. If upgrading is not immediately feasible, implement exception handling wrappers around socket write operations and error packet transmission code paths.

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.30
Opc Ua C\+\+ Software Development KitApplication
Affected:<= 6.20.1
Secure Integration ServerApplication
Affected:<= 1.22

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 the installed Softing product
    Locate the Softing software installation directory and check for product name (Softing OPC, Softing OPC UA C++ SDK, or Softing Secure Integration Server). Check version information in the program's About or version details, typically found in the installation folder or via the application's help menu.
    Affected if The product name matches one of the affected products and the version number is at or below the affected thresholds (Softing Opc <= 5.30, OPC UA C++ SDK <= 6.20.1, Secure Integration Server <= 1.22)
  2. Verify the operating system is Windows
    Check the operating system where the Softing software is running. This vulnerability specifically affects Windows environments.
    Affected if The Softing software is running on a Windows host (this is a Windows-specific flaw)
  3. Confirm OPC UA server functionality is active
    Check if the Softing application is configured as an OPC UA server and actively accepting connections. Review server configuration files or status interfaces to determine if server role is enabled.
    Affected if The software is running as an OPC UA server, as the vulnerability is triggered when the server attempts to send error packets
  4. Review application crash logs
    Examine Windows Event Viewer or application-specific log files for unhandled exception errors related to socket write operations or error packet transmission. Look for crash dumps or error reports mentioning 'exception' and 'socket' or 'write'.
    Affected if Recent crash logs show unhandled exceptions occurring during network write operations or error packet handling

You are affected if you are running any of the three listed Softing products on Windows at versions at or below the affected thresholds, with the OPC UA server functionality 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 a release after 6.20.1
Interim mitigation

Upgrade to Softing OPC UA C++ SDK version 6.30 or later, which contains the fix for this uncaught exception. If upgrading is not immediately feasible, implement exception handling wrappers around socket write operations and error packet transmission code paths.

Recommended fix High confidence

Softing OPC UA C++ SDK 6.30 or later; Secure Integration Server 1.23 or later; OPC 5.31 or later

  1. 1. Identify which Softing product(s) are in use: OPC UA C++ SDK, Secure Integration Server, or OPC
  2. 2. For OPC UA C++ SDK: Upgrade to version 6.30 or later
  3. 3. For Secure Integration Server: Upgrade to version 1.23 or later (the next version after 1.22)
  4. 4. For OPC: Upgrade to version 5.31 or later (the next version after 5.30)
  5. 5. Test the upgrade in a staging environment before deploying to production
  6. 6. Verify the application no longer crashes when the server sends error packets while socket is blocked on writing
Caveat Review release notes for any API changes between your current version and the upgrade version, as minor version jumps may include API modifications

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

Fix this in Opc Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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