CVE-2022-45790
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 FINS protocol has an authenticated feature to prevent access to memory regions. Authentication is susceptible to bruteforce attack, which may allow an adversary to gain access to protected memory. This access can allow overwrite of values including programmed logic.
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 confidenceThe Omron FINS protocol contains an authenticated feature designed to protect memory regions from unauthorized access. However, the authentication mechanism is susceptible to brute force attacks, allowing an adversary to repeatedly attempt credentials until successful. Once authenticated, an attacker can access protected memory areas and overwrite values including programmed logic in PLCs.
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< 4.1< 4.1< 4.1< 4.1< 4.1< 1.3< 1.3< 1.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 modelCheck the physical label on the PLC unit or query the PLC via CX-Programmer or sysmac Studio for the exact model number (e.g., Cj1g Cpu45p, Cp1e E, Cj2h Cpu68)Affected if The PLC model matches one of the affected models: Cj1g Cpu45p, Cj1g Cpu45p Gtc, Cj1g Cpu44p, Cj1g Cpu43p, Cj1g Cpu42p, Cp1e E, Cp1e N, or Cj2h Cpu68
-
Check the firmware versionAccess the PLC via CX-Programmer or sysmac Studio and navigate to the PLC properties or unit information to retrieve the firmware versionAffected if The firmware version is lower than 4.1 for Cj1g models, lower than 1.3 for Cp1e models, or lower than 1.5 for Cj2h Cpu68
-
Verify if FINS authentication is configuredIn CX-Programmer, go to PLC > Password Setup to check if a FINS password or authentication is set for the PLCAffected if FINS authentication is disabled or not configured on the PLC (the vulnerability requires the authentication feature to exist in order to be brute forced)
-
Check network exposure of the PLCReview network topology and firewall rules to determine if the PLC FINS protocol port (9600/UDP) is accessible from untrusted networksAffected if The PLC FINS port (UDP 9600) is directly accessible from networks outside the trusted operational technology network
-
Look for brute force authentication attemptsEnable FINS protocol logging in CX-Programmer or use a network sniffer (e.g., Wireshark) on the PLC network segment to monitor for repeated authentication attempts from the same source IPAffected if Multiple failed FINS authentication attempts followed by a successful authentication are observed in logs or network captures
The environment is affected if the PLC model and firmware version match the affected list and the FINS protocol is accessible from an untrusted network.
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.31.54.1
Implement network segmentation to isolate PLCs from untrusted networks, apply rate limiting or account lockout mechanisms to the FINS authentication, and apply vendor patches when available. Consider deploying intrusion detection to identify brute force patterns.
Cj1g series to firmware >= 4.1, Cp1e E/N to firmware >= 1.3, Cj2h Cpu68 to firmware >= 1.5
- Identify the specific Omron controller model (Cj1g Cpu45p, Cj1g Cpu44p, Cj1g Cpu43p, Cj1g Cpu42p, Cp1e E, Cp1e N, or Cj2h Cpu68) from the affected product list
- Obtain the firmware update from the official Omron support portal (www.fa.omron.co.jp) or through your Omron representative
- Follow Omron's standard firmware update procedure for the specific controller model - typically involves using Omron's programming software (such as CX-Programmer or Sysmac Studio)
- Ensure the PLC is in PROGRAM mode before initiating firmware update
- Transfer the new firmware file to the controller via the programming software or SD card method specific to the model
- After firmware update, verify the FINS protocol authentication is no longer susceptible to brute force attacks
- Test that legitimate FINS protocol authentication functions correctly with the updated firmware
- If applicable, implement network segmentation to limit exposure to FINS protocol interfaces during the remediation period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45790 — 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-45790 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