CVE-2022-44018
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 · uneditedIn Softing uaToolkit Embedded before 1.40.1, a malformed PubSub discovery announcement message can cause a NULL pointer dereference or out-of-bounds memory access in the subscriber application.
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 confidenceA memory safety vulnerability exists in Softing uaToolkit Embedded versions before 1.40.1. When a subscriber application processes a malformed OPC UA PubSub discovery announcement message, it can trigger either a NULL pointer dereference or an out-of-bounds memory access, leading to a denial-of-service condition.
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< 1.41CVSS 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 if Softing uaToolkit Embedded is installedSearch for uaToolkit Embedded components or libraries in the system, typically found in installation directories or included as a library in applications. Check for files named 'uaToolkit', 'uatoolkit', or related OPC UA components.Affected if Softing uaToolkit Embedded is present on the system
-
Determine the installed version of uaToolkit EmbeddedLocate version information in the software installation, typically found in version files, DLL/Library properties, or by querying the uaToolkit API if accessible. Compare the installed version against the affected range of versions before 1.40.1 (or < 1.41 per affected product listing).Affected if The installed version is lower than 1.40.1 (or lower than 1.41)
-
Check if OPC UA PubSub discovery feature is configuredReview application configuration files or runtime settings for OPC UA PubSub components. Look for PubSub subscription settings, discovery announcement handlers, or network configuration related to PubSub message processing.Affected if OPC UA PubSub discovery announcement processing is enabled or configured in the environment
-
Verify network exposure to PubSub discovery messagesExamine network configuration, firewall rules, or application network bindings to determine if the system accepts OPC UA PubSub discovery messages from network sources.Affected if The system can receive PubSub discovery messages from untrusted or external network sources
A user is affected if Softing uaToolkit Embedded version is below 1.40.1 AND OPC UA PubSub discovery announcement processing is enabled and accessible to potential attackers sending malformed messages.
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 · scoped1.41
Upgrade uaToolkit Embedded to version 1.40.1 or later. If immediate upgrade is not feasible, implement network segmentation to restrict PubSub discovery messages to trusted sources only.
uaToolkit Embedded version 1.41 or later
- 1. Identify the current version of Softing uaToolkit Embedded installed in your environment
- 2. Download the latest version of Softing uaToolkit Embedded (version 1.41 or later) from the official Softing industrial website
- 3. Review the release notes and migration guide for version 1.41
- 4. Create a backup of your current configuration and application data
- 5. Stop any running subscriber applications that use uaToolkit Embedded
- 6. Install version 1.41 or later of uaToolkit Embedded following the vendor's installation instructions
- 7. Verify the installation by checking the version number
- 8. Restart the subscriber applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44018 — 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-44018 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