CyberSecBulletin
CVE-2022-45794NVD status: Modified

CJ-series and CS-series CPU modules: Missing Authentication for Critical Functionality

Published Updated By the CyberSecBulletin desk

CVE-2022-45794 is a high-severity missing authentication for critical functionality vulnerability in CJ-series and CS-series CPU modules from Omron, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected CJ-series and CS-series CPU modules versions: 0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.54% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of CJ-series and CS-series CPU modules you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on fa.omron.co.jp for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
OmronCJ-series and CS-series CPU modules0Not stated
OmronSysmac Cj2h-cpu64-eip FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu64 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu65-eip FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu65 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu66-eip FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu66 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu67-eip FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu67 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu68-eip FirmwareNot specified in the recordNot stated
OmronSysmac Cj2h-cpu68 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu11 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu12 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu13 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu14 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu15 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu31 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu32 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu33 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu34 FirmwareNot specified in the recordNot stated
OmronSysmac Cj2m-cpu35 FirmwareNot specified in the recordNot stated
OmronSysmac Cj1g-cpu45p FirmwareNot specified in the recordNot stated
OmronSysmac Cj1g-cpu44p FirmwareNot specified in the recordNot stated
OmronSysmac Cj1g-cpu43p FirmwareNot specified in the recordNot stated
OmronSysmac Cj1g-cpu42p FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 17 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
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.6HighCNA (dragos.com)
CVSS 3.17.5HighNVD

Official description

An attacker with network access to the affected PLC (CJ-series and CS-series PLCs, all versions) may use a network protocol to read and write files on the PLC internal memory and memory card.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authentication for Critical Functionality

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
  • When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.

More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in CJ-series and CS-series CPU modules

All CJ-series and CS-series CPU modules vulnerabilities

Recent Missing Authentication for Critical Functionality vulnerabilities

Spotted an error? Tell us.