# CVE-2022-44018: Null dereference in n/a

> A malformed PubSub discovery message in Softing uaToolkit Embedded can cause a NULL pointer dereference, leading to denial of service in subscriber applications.

- **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:** 25 Jan 2023
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-rfrr-3g6g-x7ww

## What is CVE-2022-44018?

CVE-2022-44018 is a high-severity vulnerability in n/a, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Softing Uatoolkit Embedded.

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

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

## Is CVE-2022-44018 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45920](https://insights.sbomify.com/CVE-2022-45920/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44018 is a high-severity vulnerability in n/a, published on 25 Jan 2023. 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-44018 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-44018/ (Markdown: https://insights.sbomify.com/CVE-2022-44018/index.md)
```

## Sources

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

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