Cyber Resilience

CVE-2023-22366

Memory Safety in Omron Cx-Motion-Mch Firmware ≤ 2.33

Published
17 January 2023
Modified
03 April 2025
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0020 10th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-22366 is a high-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Omron Cx-Motion-Mch Firmware. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-38748Same vendor: Omron
CVE-2023-22322Same vendor: Omron
CVE-2024-33687Same vendor: Omron
CVE-2023-38747Same vendor: Omron
CVE-2023-22317Same vendor: Omron
CVE-2023-22277Same vendor: Omron
CVE-2023-38746Same vendor: Omron
CVE-2023-22357Same vendor: Omron
CVE-2023-27396Same vendor: Omron
CVE-2023-27385Same vendor: Omron

Affected Assets

omron
cx-motion-mch firmware
≤ 2.33

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect uninitialized pointer usage before release.

prevents

Secure development life cycle mandates practices that reduce uninitialized pointer defects.

degrades

Application security requirements can specify pointer initialization rules.

degrades

Secure architecture principles discourage unsafe pointer handling.

prevents

Secure coding standards directly prohibit use of uninitialized pointers.

References