Safeguard
Vulnerability Analysis•

CVE-2022-45794: High Missing Authentication in Omron CJ and CS PLCs

CVE-2022-45794 lets anyone with network access read and write files on Omron CJ and CS series PLCs, all versions. Isolate the controllers now.

Safeguard Security Team
3 min read

CVE-2022-45794 is a high severity (CVSS 8.6) missing authentication flaw in Omron CJ series and CS series PLCs, all versions. An attacker with network access can use a network protocol to read and write files on the controller's internal memory and memory card. No fixed version is confirmed, so isolate the devices.

What's affected

The record says all versions of the CJ series and CS series PLCs are affected. It lists CJ2H CPU models with and without the EtherNet/IP unit as the affected configurations. Because the record says all versions, there is no patched release to move to.

Omron published its own advisory as OMSR-2023-002, and Dragos covers the issue in its Omron advisory. I could not read the Omron PDF here, so use it to see which mitigations the vendor recommends for your exact model.

How to check if you're exposed

Start from your asset inventory. List every Omron CJ and CS series controller and the network it sits on. On the plant network, confirm which hosts can reach the PLC's communication ports.

A useful test is a firewall review rather than a scan of the device. If any host outside the control zone can reach the controller, the missing authentication is exposed. Avoid scanning live controllers without the plant owner's agreement, since some devices react badly to unexpected traffic.

What to do now

  1. Identify every CJ and CS series PLC, and record firmware and network location.
  2. Block access to the controllers from any network that does not need it, and never expose them to the internet.
  3. Allow only named engineering stations to talk to the PLC protocol ports.
  4. Monitor for file transfers to and from the controllers, and alert on unexpected sources.
  5. Read Omron's advisory OMSR-2023-002 and apply each mitigation it lists.

Why it matters

The weakness is CWE-306, missing authentication for a critical function. The controller's file access protocol does not ask the caller to prove who it is. Anyone who can send packets to it can use the feature.

Impact in the record is high confidentiality with a changed scope, so the damage can reach beyond the controller itself. Files on a PLC can hold program logic and configuration. The KEV flag is false and I found no advisory describing exploitation. Segmentation is the main defense here because the product itself cannot be patched out of the problem.

Quick check

Is there a patch for CVE-2022-45794?

The record says all versions are affected and I could not confirm a fixed version. Follow Omron's advisory OMSR-2023-002 for mitigations.

What is the best control?

Network isolation. Keep the PLC reachable only from the engineering systems that need it.

Sources

You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.