CVE-2022-3157
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 vulnerability exists in the Rockwell Automation controllers that allows a malformed CIP request to cause a major non-recoverable fault (MNRF) and a denial-of-service condition (DOS).
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 confidenceA malformed CIP (Common Industrial Protocol) request can be sent to vulnerable Rockwell Automation controllers, triggering a major non-recoverable fault (MNRF) that causes denial of service. The controller enters an MNRF state requiring manual intervention to recover, creating extended downtime.
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>= 20, <= 33>= 28, <= 33>= 28, <= 33>= 20, <= 33>= 20, <= 33>= 20, <= 33CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 controller model and firmware versionAccess the controller via RSLogix/Studio 5000 or the web interface. Navigate to the controller properties or system information to retrieve the exact firmware version. For command-line verification on the network, use RSLinx Classic or FactoryTalk Linx to browse to the controller and read the firmware revision.Affected if The firmware version falls within the affected ranges: CompactLogix 5370 (20-33), Compact GuardLogix 5370 (28-33), Compact GuardLogix 5380 (28-33), ControlLogix 5570 (20-33), ControlLogix 5570 Redundancy (20-33), GuardLogix 5570 (20-33).
-
Verify Ethernet/IP (CIP) communication is enabledCheck the controller's communication configuration in RSLogix/Studio 5000 under the controller properties. Confirm that the Ethernet/IP or EtherNet/IP adapter is configured and enabled. Inspect the I/O configuration to see if any Ethernet/IP modules are present.Affected if Ethernet/IP (CIP) communication is enabled and the controller is actively listening on port 44818 (EtherNet/IP).
-
Confirm controller network exposureReview network architecture documentation or perform a port scan to determine if the controller's Ethernet/IP port (44818/TCP and 2222/UDP) is accessible from untrusted network segments. Check if the controller is directly connected to corporate networks or DMZs.Affected if The controller's CIP endpoint is reachable from network segments that are not isolated or protected by strict access controls.
A user is affected if their controller model and firmware version match the listed affected products AND the controller has Ethernet/IP communication enabled and is accessible over the 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.
From vendor dataIsolate affected controllers on separate network segments with strict access controls; apply CIP security features (CIP Security Identity) to authenticate and validate CIP messages; verify with Rockwell for firmware updates addressing this vulnerability.
- Consultation12.0 h
- Implementation20.0 h
- Testing12.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 $14,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3157 — 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-3157 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