dbcve.org
Datafeed Opc SuiteApplication · Softing

CVE-2021-42262

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-11
Fix available
A fix is available. Upgrade to 5.70.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An issue was discovered in Softing OPC UA C++ SDK before 5.70. An invalid XML element in the type dictionary makes the OPC/UA client crash due to an out-of-memory condition.

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

The Softing OPC UA C++ SDK before version 5.70 contains a vulnerability where malformed XML elements in the type dictionary trigger an out-of-memory condition, causing the OPC/UA client to crash. This is a denial-of-service vulnerability exploitable by sending specially crafted invalid XML data to a vulnerable client.

MitigationUpgrade the Softing OPC UA C++ SDK to version 5.70 or later to receive the patch for this vulnerability. Additionally, implement input validation on received type dictionaries before processing.

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
Datafeed Opc SuiteApplication
Affected:<= 5.19
Opc Ua C\+\+ Software Development KitApplication
Affected:>= 5.56.0, < 5.70.0
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Softing product
    Check the system for installed Softing OPC UA software. Common installation paths include C:\Program Files\Softing or /opt/softing. Look for executable files such as DatafeedOpcSuite.exe, SecureIntegrationServer.exe, or ua-sdk libraries.
    Affected if Any Softing OPC UA product is installed and the version falls within the affected ranges.
  2. Check Datafeed OPC Suite version
    If Datafeed Opc Suite is installed, locate the executable or check the installed programs list. Right-click the DatafeedOpcSuite.exe, go to Properties, and check the File Version under the Details tab. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Softing Datafeed entry.
    Affected if The installed version is 5.19 or lower.
  3. Check OPC UA C++ SDK version
    If the Softing OPC UA C++ SDK is embedded in a custom application, check the version of the SDK libraries (typically opcua_sdk.dll, opcua_core.dll, or similar). Inspect the file properties or check the SDK documentation/version file shipped with the application.
    Affected if The SDK version is 5.56.0 or higher but lower than 5.70.0.
  4. Check Secure Integration Server version
    If Softing Secure Integration Server is installed, locate the executable and check its version through Properties or the application interface.
    Affected if The installed version is 1.22 or lower.
  5. Verify OPC UA client service is active
    Check if the Softing OPC UA client service is running. On Windows, open Services console and look for Softing Datafeed OPC Suite or similar service. On Linux, check running processes for the product daemon.
    Affected if The OPC UA client service is actively running and processing type dictionaries from remote servers.

A system is affected if it runs any Softing OPC UA product (Datafeed OPC Suite, OPC UA C++ SDK, or Secure Integration Server) with a version matching the affected ranges and has OPC UA client functionality enabled to receive type dictionaries.

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 5.70.0 or later
Fixed in 5.70.0
Interim mitigation

Upgrade the Softing OPC UA C++ SDK to version 5.70 or later to receive the patch for this vulnerability. Additionally, implement input validation on received type dictionaries before processing.

Recommended fix Moderate confidence

OPC UA C++ SDK: 5.70.0 or later; Datafeed Opc Suite: newer than 5.19; Secure Integration Server: newer than 1.22

  1. Identify the specific Softing product in use (Datafeed Opc Suite, OPC UA C++ SDK, or Secure Integration Server)
  2. For OPC UA C++ SDK: Upgrade to version 5.70.0 or later which contains the fix for the invalid XML element vulnerability
  3. For Datafeed Opc Suite: Upgrade to a version newer than 5.19 that incorporates the SDK fix (contact Softing support to confirm which version includes the patch)
  4. For Secure Integration Server: Upgrade to a version newer than 1.22 that incorporates the SDK fix (contact Softing support to confirm which version includes the patch)
  5. After upgrading, validate that the OPC/UA client no longer crashes when processing type dictionaries with XML elements
Caveat Upgrading the SDK may introduce API changes; test thoroughly in a non-production environment before deploying

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

Fix this in Datafeed Opc Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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