# CVE-2022-25302: Denial of Service (DoS)

> Attackers can cause denial of service in ASNeG/OpcUaStack by sending crafted OPC UA messages with special encoded NodeIds.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v987-x2f9-r6gr

## What is CVE-2022-25302?

CVE-2022-25302 is a high-severity denial of service vulnerability in ASNeG/OpcUaStack, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All 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.

## Which versions are affected by CVE-2022-25302?

It affects 1 product.


Products: Opc Ua Stack Project Opc Ua Stack.

## How do I fix CVE-2022-25302?

No fix has been published for CVE-2022-25302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-25302 being exploited?

There is no known exploitation of CVE-2022-25302 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25302 and fix it if it is affected.

What it is: CVE-2022-25302 is a high-severity denial of service vulnerability in ASNeG/OpcUaStack, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25302 in the wild and no public exploit code.

Affected product: ASNeG/OpcUaStack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25302/ (Markdown: https://insights.sbomify.com/CVE-2022-25302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25302
- OSV: https://osv.dev/vulnerability/CVE-2022-25302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25302/
Summaries are generated and may contain mistakes; the official description above is the record.