CVE-2022-45794
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 · uneditedAn 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.
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 · moderate confidenceAn unauthenticated attacker with network access to affected Omron CJ-series or CS-series PLCs can exploit a network protocol vulnerability to read and write files directly to the PLC's internal memory and removable memory cards, allowing potential manipulation of PLC logic and configuration.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the PLC model and firmware versionConnect to the PLC via Sysmac Studio or use network discovery tools (such as Omron NJ-series network configurator or FINS over Ethernet) to query the PLC for its model number and firmware version. The affected models are Sysmac CJ2h CPU64, CPU65, CPU66, and CPU67 variants, with or without Eip suffix.Affected if The PLC model is any of the following: CJ2h CPU64, CJ2h CPU64 Eip, CJ2h CPU65, CJ2h CPU65 Eip, CJ2h CPU66, CJ2h CPU66 Eip, CJ2h CPU67, or CJ2h CPU67 Eip.
-
Determine if EtherNet/IP protocol is enabledCheck the PLC configuration in Sysmac Studio under the EtherNet/IP settings, or query the PLC over the network for its EtherNet/IP interface configuration. The vulnerability can be exploited via the network protocol regardless of Eip designation, but Eip models support EtherNet/IP which may be the attack vector.Affected if The PLC has EtherNet/IP functionality enabled and is connected to the network.
-
Verify network accessibility of the PLCPerform a network scan to confirm the PLC has an IP address and is reachable on the network. Use standard network diagnostic tools (ping, nmap) or PLC-specific tools to probe for open ports associated with Omron PLC protocols (FINS ports 9600/TCP, EtherNet/IP port 44818/TCP).Affected if The PLC is reachable from network segments that contain untrusted or attacker-controlled systems.
-
Confirm PLC is not isolated behind protective network infrastructureReview network architecture diagrams and firewall rules to determine if the PLC is placed in a dedicated VLAN, behind a firewall, or on an isolated network segment separate from corporate or untrusted networks.Affected if The PLC is directly accessible from untrusted network segments without firewall filtering or network segmentation.
Your environment is affected if you have any Omron Sysmac CJ2h CPU64/65/66/67 PLCs (Eip or non-Eip variants) with any firmware version that are network-accessible from untrusted segments, as the vulnerability affects all versions of these models.
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.
From vendor dataImplement network segmentation to isolate PLCs from untrusted networks, place PLCs behind firewalls or in dedicated VLANs, and apply compensating controls until vendor firmware updates are available.
- Consultation12.0 h
- Implementation20.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 $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45794 — 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-45794 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