# CVE-2022-39823: Use after free in n/a

> A use-after-free vulnerability in the Softing OPC UA C++ SDK allows attackers to cause denial of service or execute arbitrary code via crafted browse requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-6mw3-7v65-29gj

## What is CVE-2022-39823?

CVE-2022-39823 is a high-severity use after free vulnerability in n/a, published on 20 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Softing OPC UA C++ SDK 5.66 through 6.x before 6.10. An OPC/UA browse request exceeding the server limit on continuation points may cause a use-after-free error

Weakness: CWE-416 (Use After Free)

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

It affects 2 products.


Products: Softing Opc, Softing Opc Ua C\+\+ Software Development Kit.

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

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

## Is CVE-2022-39823 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14524](https://insights.sbomify.com/CVE-2020-14524/): Softing Industrial Automation OPC (critical 9.8)
- [CVE-2023-41151](https://insights.sbomify.com/CVE-2023-41151/): Denial of service in n/a (high 7.5)
- [CVE-2023-37572](https://insights.sbomify.com/CVE-2023-37572/): Missing authorization in n/a (high 7.5)
- [CVE-2020-14522](https://insights.sbomify.com/CVE-2020-14522/): Softing Industrial Automation OPC (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39823 is a high-severity use after free vulnerability in n/a, published on 20 Oct 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-39823 in the wild and no public exploit code.

Affected product: n/a. 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-39823/ (Markdown: https://insights.sbomify.com/CVE-2022-39823/index.md)
```

## Sources

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

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