CVE-2023-22357
Omron Cp1L-El20Dr-D Firmware
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-22357 is a critical-severity Active Debug Code (CWE-489) vulnerability in Omron Cp1L-El20Dr-D Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-22357 affects all versions of the OMRON CP1L-EL20DR-D programmable logic controller and stems from the presence of active debug code. This flaw permits execution of an unspecified command outside the documented FINS protocol without any authentication, exposing the device to unauthenticated network access.
A remote attacker with no credentials can leverage the issue to read from or write to arbitrary regions of device memory. Successful exploitation can result in firmware overwrite that produces a denial-of-service condition or in the execution of attacker-supplied code, consistent with the CVSS 9.8 rating reflecting network attack vector, low complexity, and full impact on confidentiality, integrity, and availability.
Public advisories published by JVN detail the vulnerability and are available at the referenced URLs. The associated EPSS score reached a modest peak of 0.0509 before receding to its current value of 0.0305, indicating limited but observable post-disclosure interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-26520
Vulnerability Data
Active debug code exists in OMRON CP1L-EL20DR-D all versions, which may lead to a command that is not specified in FINS protocol being executed without authentication. A remote unauthenticated attacker may read/write in arbitrary area of the device memory, which…
more
may lead to overwriting the firmware, causing a denial-of-service (DoS) condition, and/or arbitrary code execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.
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.
Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.
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.
Security testing in development and acceptance catches active debug code before deployment.
Configuration management can disable or remove debug features through hardened baselines.
Secure development life cycle mandates removal of debug code before release.
Secure coding standards explicitly prohibit leaving debug code active in production.
Separation of environments reduces risk of debug code reaching production but does not directly address its removal.
Change management can enforce removal of debug code as part of release gates.