CVE-2022-25302
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 · uneditedAll versions of package asneg/opcuastack are vulnerable to Denial of Service (DoS) due to a missing handler for failed casting when unvalidated data is forwarded to boost::get function in OpcUaNodeIdBase.h. Exploiting this vulnerability is possible when sending a specifically crafted OPC UA message with a special encoded NodeId.
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 confidenceThe opcuastack package fails to validate data before passing it to boost::get() in OpcUaNodeIdBase.h. When a specially crafted OPC UA message containing an incorrectly encoded NodeId is received, the boost::get casting fails without proper exception handling, causing the application to crash and resulting in 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 dataall versionsCVSS 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 opcuastack is installedSearch for opcuastack library files or packages in the system (e.g., dpkg -l, rpm -qa, find /usr -name '*opc*ua*', or check build artifacts)Affected if The opcuastack library or any application using it is present in the environment
-
Verify the opcuastack versionCheck the installed version of the opcuastack package or library (if a package manager was used)Affected if Any version of Opc Ua Stack is installed, as all versions are affected according to the CVE
-
Confirm OPC UA services are runningIdentify running processes that handle OPC UA protocol (look for processes named opcua, opcuaserver, opcuaclient, or custom applications using OPC UA)Affected if An OPC UA server or client service is actively running and processing OPC UA connections
-
Inspect OpcUaNodeIdBase.h for exception handlingLocate OpcUaNodeIdBase.h in the opcuastack source code and examine the boost::get() call for missing try-catch blocks around the NodeId casting operationAffected if The code lacks proper exception handling around boost::get() for NodeId casting, which is the vulnerable condition
-
Check OPC UA message processing logsReview application logs for crashes or exceptions occurring during OPC UA NodeId parsing, particularly messages indicating unhandled boost::get exceptionsAffected if The application experiences crashes or unhandled exceptions when receiving OPC UA messages with encoded NodeIds
A user is affected if they have any version of opcuastack running an OPC UA server or client that processes incoming OPC UA messages, as the lack of exception handling around boost::get() will cause crashes when malformed NodeIds are received.
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.
From vendor dataImplement proper input validation and exception handling around the boost::get() call in OpcUaNodeIdBase.h to gracefully handle casting failures from malformed NodeId data. Validate all NodeId encoding before processing.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25302 — 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-25302 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