# CVE-2023-22366: Null dereference in CX-Motion-MCH

> An attacker can achieve arbitrary code execution or information disclosure by tricking a user into opening a malicious project file in OMRON CX-Motion-MCH.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-8cxj-vc9j-xq64

## What is CVE-2023-22366?

CVE-2023-22366 is a high-severity vulnerability in OMRON Corporation CX-Motion-MCH, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CX-Motion-MCH v2.32 and earlier contains an access of uninitialized pointer vulnerability. Having a user to open a specially crafted project file may lead to information disclosure and/or arbitrary code execution.

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2023-22366?

It affects 1 product.


Products: Omron Cx-Motion-Mch Firmware.

## How do I fix CVE-2023-22366?

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

## Is CVE-2023-22366 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22366 and fix it if it is affected.

What it is: CVE-2023-22366 is a high-severity vulnerability in OMRON Corporation CX-Motion-MCH, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22366 in the wild and no public exploit code.

Affected product: OMRON Corporation CX-Motion-MCH. 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-2023-22366/ (Markdown: https://insights.sbomify.com/CVE-2023-22366/index.md)
```

## Sources

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

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