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

> An attacker can cause denial of service by sending unlimited large chunks without closing the session, affecting OPC UA stack users.

- **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:** 16 Sep 2024
- **Also known as:** GHSA-j5h2-937f-wv3w

## What is CVE-2022-24381?

CVE-2022-24381 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 limitation on the number of received chunks - per single session or in total for all concurrent sessions. An attacker can exploit this vulnerability by sending an unlimited number of huge chunks (e.g. 2GB each) without sending the Final closing chunk.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Asneg Opc Ua Stack.

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

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

## Is CVE-2022-24381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24381 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-24381 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-24381/ (Markdown: https://insights.sbomify.com/CVE-2022-24381/index.md)
```

## Sources

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

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