CVE-2022-31206
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 · uneditedThe Omron SYSMAC Nx product family PLCs (NJ series, NY series, NX series, and PMAC series) through 2022-005-18 lack cryptographic authentication. These PLCs are programmed using the SYMAC Studio engineering software (which compiles IEC 61131-3 conformant POU code to native machine code for execution by the PLC's runtime). The resulting machine code is executed by a runtime, typically controlled by a real-time operating system. The logic that is downloaded to the PLC does not seem to be cryptographically authenticated, allowing an attacker to manipulate transmitted object code to the PLC and execute arbitrary machine code on the processor of the PLC's CPU module in the context of the runtime. In the case of at least the NJ series, an RTOS and hardware combination is used that would potentially allow for memory protection and privilege separation and thus limit the impact of code execution. However, it was not confirmed whether these sufficiently segment the runtime from the rest of the RTOS.
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 confidenceOmron SYSMAC Nx PLCs (NJ, NY, NX, PMAC series) lack cryptographic authentication for downloaded logic code. Attackers can manipulate the object code transmitted from SYSMAC Studio to the PLC runtime, allowing injection and execution of arbitrary machine code on the CPU module.
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< 1.29< 1.29< 1.29< 1.29< 1.29< 1.29< 1.49< 1.49CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the PLC model and seriesConnect to the PLC via Sysmac Studio or check the device nameplate to confirm the exact model (e.g., Nx701-1600, Nx701-1620, Nj101-1000, Nj101-1020, or other NJ/NY/NX/PMAC series variants)Affected if The PLC is any Omron NJ, NY, NX, or PMAC series controller and the model matches one of the affected variants listed in the CVE
-
Check the installed firmware versionUse Sysmac Studio to connect to the PLC and view the Unit Information or check the CPU module directly for the firmware version numberAffected if For Nx701 models (1600, 1620, 1700, 1720, Z600, Z700): firmware version is less than 1.29. For Nj101 models (1000, 1020): firmware version is less than 1.49
-
Determine PLC network accessibilityReview network configuration and firewall rules to check if the PLC is directly accessible from any network segment outside the control system DMZAffected if The PLC has an exposed Ethernet/IP or Omron FINS interface reachable from untrusted networks, as this allows an attacker to intercept or inject logic code during transfer
-
Verify if code download from Sysmac Studio is possible without authenticationAttempt to establish a connection from Sysmac Studio to the PLC and observe whether cryptographic verification of transferred logic code is performed or requestedAffected if Sysmac Studio can transfer logic code to the PLC without any cryptographic authentication or integrity verification prompt, indicating the vulnerable unauthenticated code transfer is in use
-
Check for change detection or integrity monitoringReview if any network monitoring, IDS, or PLC change detection system is in place to detect unauthorized modifications to PLC logic or unexpected code downloadsAffected if No integrity monitoring or change detection solution is deployed, meaning any injected malicious code would go unnoticed
The environment is affected if any Omron NJ/NY/NX/PMAC PLC (particularly Nx701 series with firmware <1.29 or Nj101 series with firmware <1.49) is in use and is network-accessible without cryptographic authentication for logic code downloads from Sysmac Studio.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.291.49
Isolate PLCs behind network segmentation; apply vendor firmware updates when available; implement compensating controls such as network monitoring and change detection for PLC logic modifications.
Nx701 series: Firmware 1.29 or later | Nj101 series: Firmware 1.49 or later
- Identify the specific Omron PLC model (Nx701 series or Nj101 series) in your environment
- Determine the current firmware version of the affected PLC(s)
- For Nx701 series (1600, 1620, 1700, 1720, Z600, Z700): Upgrade firmware to version 1.29 or later
- For Nj101 series (1000, 1020): Upgrade firmware to version 1.49 or later
- Obtain firmware from official Omron sources (e.g., Omron customer portal or authorized distributors)
- Follow Omron's documented firmware update procedure, which typically involves connecting via Ethernet using SYSMAC Studio or a dedicated firmware update tool
- Verify the firmware upgrade was successful and the PLC is functioning normally
- After upgrade, ensure network segmentation and access controls are in place as defense-in-depth measures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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