CVE-2022-1797
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 · uneditedA malformed Class 3 common industrial protocol message with a cached connection can cause a denial-of-service condition in Rockwell Automation Logix Controllers, resulting in a major nonrecoverable fault. If the target device becomes unavailable, a user would have to clear the fault and redownload the user project file to bring the device back online.
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 confidenceA malformed Class 3 Common Industrial Protocol (CIP) message sent over a cached connection to Rockwell Automation Logix Controllers triggers a major nonrecoverable fault, causing a denial-of-service condition that renders the device unavailable until manual intervention.
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< 33.011< 33.011< 33.011< 33.011< 33.011< 34.011< 34.011< 34.011CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 controller modelLocate the controller hardware nameplate or check the controller properties in Studio 5000/RsLogix 5000 to determine if the device is a CompactLogix 5370, 5380, or 5480; Controllogix 5570 or 5580; or Guardlogix 5580 variantAffected if The controller model matches one of the affected product families (CompactLogix 5370/5380/5480, Controllogix 5570/5580, Guardlogix 5580, or Compact Guardlogix 5370/5380)
-
Determine the firmware versionConnect to the controller via RSLinx Classic or FactoryTalk Linx, then use RSLogix 5000/Studio 5000 to view the controller properties, or query the controller firmware version through the web interface if availableAffected if The installed firmware version is below 33.011 for 5380/5480/5580/Guardlogix 5380 models, or below 34.011 for 5370/5570/Compact Guardlogix 5370 models
-
Verify CIP cached connections are enabledReview the controller's communication settings in RSLogix 5000/Studio 5000 under the controller properties or connection configuration, or inspect the CIP communication path configuration to determine if cached connections are permitted for Class 3 messagingAffected if CIP Class 3 cached connections are enabled and accessible from untrusted network segments
-
Check network exposureReview network architecture diagrams and firewall rules to determine if the controller's CIP port (typically 2222 for EtherNet/IP) is exposed to untrusted or external network segmentsAffected if The controller CIP interface is reachable from untrusted network segments without firewall filtering
A user is affected if they have a vulnerable Logix controller model running firmware below the patched versions AND that controller has CIP cached connections accessible from a network where a malformed Class 3 CIP message could be sent.
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 · scoped33.01134.011
Apply Rockwell's firmware patches for affected Logix controllers and implement network segmentation to restrict untrusted CIP traffic; ensure incident response procedures include the manual fault clearance and project redownload recovery steps.
Compactlogix 5380/5480/Controllogix 5580/Guardlogix 5580: firmware >= 33.011 | Compactlogix 5370/Compact Guardlogix 5370/Controllogix 5570: firmware >= 34.011
- Identify the exact model and current firmware version of the affected Logix controller using RSLinx Classic or FactoryTalk View
- Backup the current project file and controller configuration to ensure data can be restored if needed
- Review release notes for the target firmware version (33.011 for 5380/5480/5580 series, 34.011 for 5370/5570 series) to understand any changes or requirements
- Download the appropriate firmware update from the Rockwell Automation Product Compatibility and Download Center (PCDC) at rockwellautomation.custhelp.com
- Use ControlFLASH or ControlFLASH Plus tool to update the controller firmware to version 33.011 or higher for 5380/5480/5580 controllers, or 34.011 or higher for 5370/5570 controllers
- After firmware update, clear any existing faults on the controller
- Verify the controller returns to RUN mode and functions correctly
- Re-download the user project file if required to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1797 — 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-1797 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