CJ1M SYSMAC CJ-series: Improper Access Control
CVE-2023-0811 is a critical-severity improper access control vulnerability in CJ1M SYSMAC CJ-series from Omron, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected CJ1M SYSMAC CJ-series versions: All versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of CJ1M SYSMAC CJ-series you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on ia.omron.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Omron | CJ1M SYSMAC CJ-series | All versions | Not stated |
| Omron | CJ1M SYSMAC CS-series | All versions | Not stated |
| Omron | CJ1M SYSMAC CP-series | All versions | Not stated |
| Omron | Sysmac Cj2h-cpu64 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu64-eip Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu65 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu65-eip Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu66 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu66-eip Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu67 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu67-eip Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu68 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2h-cpu68-eip Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu11 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu12 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu13 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu14 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu15 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu31 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu32 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu33 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu34 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cj2m-cpu35 Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cp1e-e10dr-a Firmware | Not specified in the record | Not stated |
| Omron | Sysmac Cp1e-e10dr-d Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.1 | Critical | NVD |
Official description
Omron CJ1M unit v4.0 and prior has improper access controls on the memory region where the UM password is stored. If an adversary issues a PROGRAM AREA WRITE command to a specific memory region, they could overwrite the password. This may lead to disabling UM protections or setting a non-ASCII password (non-keyboard characters) and preventing an engineer from viewing or modifying the user program.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- cisa.gov/news-events/ics-advisories/icsa-23-073-01Third Party Advisory, US Government Resource
Recent Improper Access Control vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 7.3 High severity
- 8.8 High severity
- 7.2 High severity
- 7.5 High severity
Spotted an error? Tell us.