dbcve.org
Datafeed Opc SuiteApplication · Softing

CVE-2021-40871

HIGH · 7.5 CVSS v3.1 Published 2021-11-10
Fix available
A fix is available. Upgrade to 5.18 / 5.66 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 Industrial Automation OPC UA C++ SDK before 5.66. Remote attackers to cause a denial of service (DoS) by sending crafted messages to a OPC/UA client. The client process may crash unexpectedly because of a wrong type cast, and must be restarted.

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

A type cast vulnerability in Softing Industrial Automation OPC UA C++ SDK before version 5.66 allows remote attackers to crash the client process by sending crafted OPC/UA messages, causing a denial of service that requires manual restart.

MitigationUpgrade the OPC UA C++ SDK to version 5.66 or later to address the type cast vulnerability.

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.18
OpcApplication
Affected:< 5.66
Secure Integration ServerApplication
Affected:<= 1.22
Th ScopeApplication
Affected:>= 3.5

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 installed Softing OPC UA products
    Check system for installed Softing Industrial Automation products: look for 'Softing Datafeed OPC Suite', 'Softing OPC', 'Softing Secure Integration Server', or 'Softing Th Scope' in installed programs list, service list, or common installation directories (C:\Program Files\Softing or C:\Program Files (x86)\Softing on Windows, /opt/softing or /usr/local/softing on Linux)
    Affected if Any Softing product from the list is installed and the OPC UA client or server component is in use
  2. Check Softing Datafeed OPC Suite version
    If installed, check version: open the product UI and look for 'About' or 'Help > About', or check the installed version in Windows Add/Remove Programs, or run 'datafeed_opc_suite -v' from command line if available, or inspect the executable properties of the main service executable
    Affected if Version is less than 5.18
  3. Check Softing OPC version
    If installed, check version: open the product UI and navigate to Help > About, or check the Windows Add/Remove Programs entry, or run 'opc -v' from command line if available, or inspect the main executable file properties
    Affected if Version is less than 5.66
  4. Check Softing Secure Integration Server version
    If installed, check version: open the management console and look for version info, or check the Windows Add/Remove Programs entry, or inspect the service executable properties (commonly SecureIntegrationServer.exe)
    Affected if Version is 1.22 or lower
  5. Check Softing Th Scope version
    If installed, check version: open the application and go to Help > About, or check the Windows Add/Remove Programs entry, or inspect the thscope.exe file properties
    Affected if Version is 3.5 or any version 3.5 and above

User is affected if any of the four Softing products are installed with a version matching the affected ranges listed, and the OPC UA client or server functionality is actively being used 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
Upgrade available Upgrade to 5.18 / 5.66 or later
Fixed in 5.185.66
Interim mitigation

Upgrade the OPC UA C++ SDK to version 5.66 or later to address the type cast vulnerability.

Recommended fix High confidence

OPC UA C++ SDK 5.66+ | Datafeed Opc Suite 5.18+ | Secure Integration Server >1.22

  1. Upgrade the Softing Industrial OPC UA C++ SDK to version 5.66 or later
  2. If using Datafeed Opc Suite, upgrade to version 5.18 or later
  3. If using Secure Integration Server, upgrade to version greater than 1.22 (e.g., 1.23 or later)
  4. After upgrading, restart any affected OPC/UA client services to load the fixed libraries
  5. Verify the upgrade by testing OPC/UA client functionality with normal operations
Caveat Review Softing release notes for any API or configuration changes between your current version and 5.66+

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

Fix this in Datafeed Opc Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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