CVE-2022-37453
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 · uneditedAn issue was discovered in Softing OPC UA C++ SDK before 6.10. A buffer overflow or an excess allocation happens due to unchecked array and matrix bounds in structure data types.
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 confidenceThe Softing OPC UA C++ SDK before version 6.10 contains a memory safety vulnerability where unchecked array and matrix bounds in structure data types can lead to buffer overflows or excess memory allocation. This occurs when the SDK processes structured data types without validating array/matrix dimensions before memory operations, potentially allowing attackers to corrupt memory or cause denial-of-service via specially crafted OPC UA messages.
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<= 3.50<= 3.50<= 5.22<= 6.00<= 1.22<= 1.74CVSS 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.
-
Identify installed Softing product and versionLocate the Softing software installation directory and check the version information file, or run the product's version command (e.g., 'opcua version' or check the About dialog in the management interface). Compare the version number to the affected ranges: Edgeaggregator <= 3.50, Edgeconnector <= 3.50, Opc <= 5.22, OPC UA C++ SDK <= 6.00, Secure Integration Server <= 1.22, Uagates <= 1.74.Affected if The installed version is at or below the affected version for your specific product.
-
Confirm OPC UA SDK library versionIf using the C++ SDK directly, locate the shared library files (such as libopcua.so, opcua_sdk.dll, or similar) and check their embedded version information using tools like 'strings', 'file', or the library's built-in version query function.Affected if The SDK library version is 6.10 or lower.
-
Verify OPC UA server or client is processing structured data typesReview the application configuration or data type definition files (typically XML or JSON files defining custom OPC UA structure data types) to identify if any structures include array or matrix fields. Check application logs for references to 'Structure', 'DataType', or custom type handling.Affected if The application uses custom OPC UA structure data types that include array or matrix dimensions.
-
Inspect network traffic for OPC UA structure messagesCapture and analyze OPC UA network traffic (using Wireshark or similar tools) and look for browse responses, read responses, or subscription data containing structure data types with array dimensions in the encoding.Affected if Incoming OPC UA messages contain structure data types with array or matrix specifications that reach the SDK for processing.
You are affected if your installed Softing product version is at or below the affected range AND your system processes OPC UA structured data types with array or matrix dimensions through the vulnerable SDK code.
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 · scopedUpgrade the Softing OPC UA C++ SDK to version 6.10 or later which implements proper bounds checking. For systems unable to upgrade immediately, implement input validation on all incoming OPC UA structure data to reject messages with out-of-bounds array/matrix specifications.
Edgeaggregator >= 3.51, Edgeconnector >= 3.51, Opc >= 5.23, OPC UA C++ SDK >= 6.10, Secure Integration Server >= 1.23, Uagates >= 1.75
- Identify which Softing product(s) are in use from: Edgeaggregator, Edgeconnector, Opc, OPC UA C++ SDK, Secure Integration Server, or Uagates
- For Edgeaggregator: upgrade to version 3.51 or later
- For Edgeconnector: upgrade to version 3.51 or later
- For Opc: upgrade to version 5.23 or later
- For OPC UA C++ SDK: upgrade to version 6.10 or later
- For Secure Integration Server: upgrade to version 1.23 or later
- For Uagates: upgrade to version 1.75 or later
- Consult product-specific release notes to verify the security fix is included and check for any migration considerations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37453 — 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-2022-37453 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