dbcve.org
Sysmac Cs1 FirmwareOperating system · Omron

CVE-2022-31204

HIGH · 7.5 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to 1.5 / 1.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Omron CS series, CJ series, and CP series PLCs through 2022-05-18 use cleartext passwords. They feature a UM Protection setting that allows users or system integrators to configure a password in order to restrict sensitive engineering operations (such as project/logic uploads and downloads). This password is set using the OMRON FINS command Program Area Protect and unset using the command Program Area Protect Clear, both of which are transmitted in cleartext.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Omron CS, CJ, and CP series PLCs transmit UM Protection passwords in cleartext over the network using the FINS commands Program Area Protect and Program Area Protect Clear. An attacker with network access can intercept these commands to obtain the plaintext password and gain unauthorized access to restricted engineering operations.

MitigationIsolate PLCs on a dedicated network segment with strict access controls, use a VPN or encrypted tunnel for all engineering access, and contact Omron for firmware updates that may address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sysmac Cs1 FirmwareOperating system
Affected:< 4.1
Sysmac Cj2m FirmwareOperating system
Affected:< 2.1
Sysmac Cj2h FirmwareOperating system
Affected:< 1.5
Sysmac Cp1e FirmwareOperating system
Affected:< 1.30
Sysmac Cp1h FirmwareOperating system
Affected:< 1.30
Sysmac Cp1l FirmwareOperating system
Affected:< 1.10
Cp1w Cif41 FirmwareOperating system
Affected:all versions
Cx ProgrammerApplication
Affected:< 9.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify PLC model and firmware version
    Connect to the PLC via Sysmac Studio or CX-Programmer and retrieve the firmware version from the device properties or system information. For Sysmac series, check via Sysmac Studio under 'Controller' > 'Device Settings'. For CJ/CP series, use CX-Programmer under 'PLC' > 'Device Type' or check the unit label on the hardware.
    Affected if The PLC model matches CS1, CJ2M, CJ2H, CP1E, CP1H, CP1L, or CP1W-CIF41 and the firmware version is below 4.1 (CS1), 2.1 (CJ2M), 1.5 (CJ2H), 1.30 (CP1E/CP1H), 1.10 (CP1L), or any version for CP1W-CIF41.
  2. Verify if UM Protection password is configured
    In Sysmac Studio, go to 'Controller' > 'Security' > 'UM Protection' to check if a password is set. In CX-Programmer, check under 'PLC' > 'Security' > 'UM Protection'. If no password is configured, the cleartext transmission issue does not pose a risk.
    Affected if A UM Protection password is configured on the PLC, as this enables the vulnerable Program Area Protect and Program Area Protect Clear FINS commands.
  3. Confirm FINS protocol network exposure
    Capture network traffic on the PLC's Ethernet segment using a packet sniffer (such as Wireshark) and filter for FINS protocol (UDP port 9600). Observe if Program Area Protect (command code 0x2807) or Program Area Protect Clear (command code 0x2808) commands are transmitted.
    Affected if FINS traffic is observable on the network and the PLC is accessible on the network without isolation, indicating the password could be intercepted in transit.
  4. Check CX-Programmer version if used for engineering
    Open CX-Programmer and navigate to 'Help' > 'About CX-Programmer' to view the installed version number.
    Affected if CX-Programmer version is below 9.6, as older versions may interact with PLCs using vulnerable command implementations.

You are affected if you operate any of the listed PLC models with firmware below the specified thresholds, have a UM Protection password configured, and the PLC's FINS protocol is accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5 / 1.10 / 1.30 or later
Fixed in 1.51.101.30
Interim mitigation

Isolate PLCs on a dedicated network segment with strict access controls, use a VPN or encrypted tunnel for all engineering access, and contact Omron for firmware updates that may address this vulnerability.

Recommended fix High confidence

Upgrade to firmware versions: CS1 >= 4.1, CJ2M >= 2.1, CJ2H >= 1.5, CP1E >= 1.30, CP1H >= 1.30, CP1L >= 1.10, and Cx Programmer >= 9.6

  1. 1. Identify the specific Omron PLC model (CS1, CJ2M, CJ2H, CP1E, CP1H, CP1L) and the current firmware version in your environment
  2. 2. For Cx Programmer (formerly CX-Programmer), upgrade to version 9.6 or later from Omron's official website
  3. 3. For Sysmac CS1 PLCs, upgrade firmware to version 4.1 or later
  4. 4. For Sysmac CJ2M PLCs, upgrade firmware to version 2.1 or later
  5. 5. For Sysmac CJ2H PLCs, upgrade firmware to version 1.5 or later
  6. 6. For Sysmac CP1E PLCs, upgrade firmware to version 1.30 or later
  7. 7. For Sysmac CP1H PLCs, upgrade firmware to version 1.30 or later
  8. 8. For Sysmac CP1L PLCs, upgrade firmware to version 1.10 or later
Caveat Upgrading PLC firmware may require project revalidation; ensure backup of existing project files before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sysmac Cs1 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31204 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data