dbcve.org
Datafeed Opc SuiteApplication · Softing

CVE-2021-42577

HIGH · 7.5 CVSS v3.1 Published 2022-03-11
Fix available
A fix is available. Upgrade to 5.70.0 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 before 5.70. A malformed OPC/UA message abort packet makes the client crash with a NULL pointer dereference.

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 NULL pointer dereference vulnerability exists in Softing OPC UA C++ SDK client components. When processing a malformed OPC/UA message abort packet, the client crashes due to improper NULL pointer handling.

MitigationUpgrade to Softing OPC UA C++ SDK version 5.70 or later, which contains the fix for the NULL pointer dereference in malformed message handling.

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.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
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 Datafeed Opc Suite, Softing OPC UA C++ SDK, or Softing Secure Integration Server by reviewing installed software lists, product directories, or running product-specific version commands if available
    Affected if any of the three affected products are installed
  2. Check Softing Datafeed Opc Suite version
    Locate the installed version of Datafeed Opc Suite through the product's UI, version file, or system installed programs list
    Affected if version is 5.19 or lower
  3. Check Softing OPC UA C++ SDK version
    Locate the installed version of the OPC UA C++ SDK through SDK version headers, lib files, or product documentation
    Affected if version is below 5.70.0
  4. Check Softing Secure Integration Server version
    Locate the installed version of Secure Integration Server through the product's UI, version file, or system installed programs list
    Affected if version is 1.22 or lower
  5. Confirm client component usage
    Verify that the Softing product is configured or running as an OPC UA client (versus server-only), since this vulnerability affects client components processing incoming messages
    Affected if the product is configured to operate as an OPC UA client receiving messages from external sources

If any affected Softing product is installed with a vulnerable version AND is operating as a client, the environment is vulnerable to CVE-2021-42577.

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 to Softing OPC UA C++ SDK version 5.70 or later, which contains the fix for the NULL pointer dereference in malformed message handling.

Recommended fix High confidence

OPC UA C++ SDK 5.70.0 or later; Datafeed OPC Suite 5.20 or later; Secure Integration Server 1.23 or later

  1. Identify which Softing product component is affected in your deployment (Datafeed OPC Suite, OPC UA C++ SDK, or Secure Integration Server)
  2. Obtain the fixed version from Softing's official distribution channels at softing.com or industrial.softing.com
  3. For OPC UA C++ SDK: upgrade to version 5.70.0 or later
  4. For Datafeed OPC Suite: upgrade to version 5.20 or later
  5. For Secure Integration Server: upgrade to version 1.23 or later
  6. Test the upgrade in a non-production environment before deploying
  7. Verify the vulnerability is resolved by confirming the client no longer crashes on malformed OPC/UA message abort packets
Caveat Review Softing release notes for any API changes or migration requirements between your current version and the target version

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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