CVE-2022-45790 is a high severity weakness in Omron CJ, CS and CP series PLCs: FINS memory protection passwords have no rate limit and can be brute forced. NVD scores it 8.6, CISA says 7.5. Update to Omron's fixed firmware and keep controllers off the internet.
What's affected
The CISA advisory ICSA-23-262-05, released 19 September 2023, lists these affected products and versions:
- Smart Security Manager: versions 1.4 and prior to 1.31, and 1.5 and prior
- CJ2H-CPU (EIP variants): version 1.4 and prior
- CJ2M-CPU: version 2.0 and prior
- CS1H and CS1G-CPU H, CJ1G-CPU P: version 4.0 and prior
- CS1D-CPU H and CPU P: version 1.3 and prior
- CS1D-CPU S: version 2.0 and prior
- CP1E-E and CP1E-N: version 1.2 and prior
CISA lists these fixed versions: CJ2H-CPU 1.5, CJ2M-CPU 2.1, CS1H/G-CPU H and CJ1G-CPU P 4.1, CS1D-CPU H and P 1.4, CS1D-CPU S 2.1 and CP1E-E and N 1.3. Updated versions come from Omron's Customer Care Team.
The sources disagree on severity and class. The NVD record scores the flaw 8.6 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N and classifies it as CWE-307 (Improper Restriction of Excessive Authentication Attempts). CISA's advisory scores it 7.5 with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, focused on obtaining sensitive information in memory, and classifies it as CWE-799 (Improper Control of Interaction Frequency). Both place it in the high range. The NVD record describes the possible outcome as overwriting values, including programmed logic, while CISA describes information disclosure, so read both when you assess the risk.
How to check if you're exposed
Identify which controller models you run and read the firmware version from the programming software or the controller's information screen, then compare it with the lists above.
Then check network reach. FINS is a network protocol, so ask which hosts can send FINS traffic to each controller. The question is whether any path leads from an IT network, a remote access system or the internet to the controllers. Your network team can test this with a firewall rule review or a scan from an untrusted segment toward the controllers' FINS port, done only with change approval, because scanning industrial devices can disrupt them.
What to do now
- Inventory Omron CJ, CS and CP controllers and Smart Security Manager installations, with their firmware versions.
- Contact Omron's Customer Care Team for the updated firmware listed in CISA's advisory, and plan the update for a maintenance window.
- Make sure the controllers are not reachable from the internet, and isolate control networks behind firewalls away from business networks.
- Where remote access is needed, use a VPN, kept current, as CISA advises.
- Monitor FINS traffic for repeated failed authentication attempts and for traffic from unexpected sources.
- Do impact analysis and a risk assessment before deploying defensive changes, as CISA reminds.
Why it matters
Programmable logic controllers run physical processes. FINS offers a password that protects memory regions, but the controllers do not limit how often passwords can be guessed. That is the heart of the issue. With unlimited guesses over the network, a short or simple password falls, and access to protected memory follows. The NVD record says that access could allow overwriting values, including programmed logic. CISA frames the outcome as reading sensitive information from memory.
The remedy has two layers. The firmware update fixes the controller, and network isolation protects the many controllers that stay on old firmware for years because updates are hard to schedule. The CISA advisory credits a researcher at Dragos with reporting the flaw. The record's KEV flag is false, and neither source reports exploitation.
Quick check
Which severity is right, 8.6 or 7.5?
Both are published. NVD's record says 8.6 and CISA's advisory says 7.5. They describe different outcomes. Both are in the high range.
Do I need to update if my controllers are isolated?
Isolation lowers the risk a lot, but CISA's advice includes both. Update when you can schedule it.
Sources
References from the NVD record that I could not retrieve: the Omron security advisory OMSR-2023-010 and the Dragos advisory page.
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.