CVE-2021-32994
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 · uneditedSofting OPC UA C++ SDK (Software Development Kit) versions from 5.59 to 5.64 exported library functions don't properly validate received extension objects, which may allow an attacker to crash the software by sending a variety of specially crafted packets to access several unexpected memory locations.
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 confidenceSofting OPC UA C++ SDK versions 5.59-5.64 contain exported library functions that fail to properly validate received extension objects. This lack of input validation allows remote attackers to send specially crafted packets containing malformed extension objects, causing the software to crash by accessing unexpected memory locations.
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>= 5.59.0, < 5.65.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Softing OPC UA C++ SDK installationSearch for Softing OPC UA SDK files on the system. Common installation paths include C:\Program Files\Softing\OPC-UA\ or /opt/softing/opcua/. Look for SDK libraries such as softingopcuasdk.dll, libsoftingopcua.so, or associated header files.Affected if The SDK files are present on the system
-
Determine installed SDK versionCheck version information in SDK libraries, version.h header files, or any version.txt/readme files included with the SDK. The version typically appears in the file properties or within SDK documentation.Affected if Installed version is 5.59.x or 5.60.x or 5.61.x or 5.62.x or 5.63.x or 5.64.x (meaning version >= 5.59.0 and < 5.65.0)
-
Identify if OPC UA server or client using the SDK is network-accessibleCheck configuration files or application settings for the OPC UA endpoint. Look for endpoint URLs with accessible IP addresses or hostnames (not localhost-only). Review firewall rules to determine if the OPC UA port (typically 4840) is open to network traffic.Affected if The OPC UA service using this SDK is listening on a network interface reachable from other systems
-
Confirm SDK is processing extension objectsReview application logs or runtime configuration to confirm the OPC UA application is configured to accept or decode extension objects from remote clients or servers. This is standard OPC UA behavior but verify the application is actively running.Affected if The OPC UA application is running and configured to process OPC UA sessions from remote clients
You are affected if the Softing OPC UA C++ SDK version is 5.59.0 through 5.64.x and your OPC UA service using this SDK is network-accessible, allowing remote attackers to send malformed extension objects that could crash the application.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.65.0
Upgrade to a patched version of the Softing OPC UA C++ SDK (version 5.65 or later). If upgrading is not immediately possible, implement network-level filtering to reject unexpected extension object types at the perimeter.
5.65.0 or later
- Identify all deployments using Softing OPC UA C++ SDK versions 5.59.0 through 5.64.x
- Upgrade the Softing OPC UA C++ SDK to version 5.65.0 or later
- Rebuild and redeploy any applications that depend on the vulnerable SDK version
- Test the updated deployment to verify the vulnerability is remediated and functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-32994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-32994 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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