dbcve.org
Compactlogix 5480 FirmwareOperating system · Rockwellautomation

CVE-2022-3752

HIGH · 7.5 CVSS v3.1 Published 2022-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An unauthorized user could use a specially crafted sequence of Ethernet/IP messages, combined with heavy traffic loading to cause a denial-of-service condition in Rockwell Automation Logix controllers resulting in a major non-recoverable 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 and continue normal operation.

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 confidence

A vulnerability in Rockwell Automation Logix controllers allows remote attackers to cause denial of service via sending a specially crafted sequence of Ethernet/IP messages combined with heavy traffic loading, triggering a major non-recoverable fault that requires manual fault clearing and project redownload to recover.

MitigationImplement network segmentation and firewall rules to restrict unauthorized Ethernet/IP traffic to the Logix controllers, and monitor for anomalous traffic patterns. If available, apply vendor firmware updates.

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
Compactlogix 5480 FirmwareOperating system
Affected:>= 32.011
Compactlogix 5580 FirmwareOperating system
Affected:>= 31.011
Guardlogix 5580 FirmwareOperating system
Affected:>= 32.011
Compact Guardlogix 5380 FirmwareOperating system
Affected:>= 31.011
Compactlogix 5380 FirmwareOperating system
Affected:>= 31.011

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rockwell Automation Logix controllers on the network
    Use RSLinx Classic or network scanning tools to enumerate devices. Look for devices with vendor ID 1 (Rockwell Automation) and product type indicating Logix controllers (CompactLogix, GuardLogix).
    Affected if Any CompactLogix 5380, CompactLogix 5480, CompactLogix 5580, GuardLogix 5580, or Compact GuardLogix 5380 controllers are present in the environment.
  2. Check firmware version on identified controllers
    Open each controller in Studio 5000 Logix Designer, or view controller properties in RSLinx Classic. Navigate to the controller's General tab to view the firmware revision (for example, version 32.011 or 31.011).
    Affected if The installed firmware version falls within or above these ranges: CompactLogix 5480 >= 32.011, CompactLogix 5580 >= 31.011, GuardLogix 5580 >= 32.011, Compact GuardLogix 5380 >= 31.011, CompactLogix 5380 >= 31.011.
  3. Verify Ethernet/IP communication is enabled
    In Studio 5000 Logix Designer, open the controller properties and check the Communication Settings. Confirm that Ethernet/IP (CIP) messaging is enabled on the controller's Ethernet port. This is the default operational mode for Logix controllers.
    Affected if Ethernet/IP protocol is enabled, which is the standard configuration for these controllers to communicate on the network.
  4. Assess network exposure of controller Ethernet ports
    Scan the network for open port 44818 (Ethernet/IP TCP) and port 2222 (Ethernet/IP UDP) on the controller IP addresses. Check firewall rules and VLAN configurations to determine if these ports are accessible from untrusted network segments.
    Affected if The controller's Ethernet/IP ports (44818/TCP, 2222/UDP) are reachable from outside the protected OT network segment or from unauthorized hosts.
  5. Check for existing fault conditions on controllers
    In Studio 5000 Logix Designer, go online with each controller and examine the I/O tree for a Major Fault icon (red X). Use the Controller Tags to inspect the MSG_ERROR bits or check the fault ring via the controller's fault configuration.
    Affected if A Major Non-Recoverable Fault is currently active on the controller, or recent faults indicate a pattern consistent with the described vulnerability (DoS from malformed Ethernet/IP messages).

The environment is affected if any Logix controller with a firmware version in the listed ranges has its Ethernet/IP interface exposed to untrusted network segments, allowing attackers to send specially crafted Ethernet/IP messages combined with heavy traffic to trigger a DoS condition.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network segmentation and firewall rules to restrict unauthorized Ethernet/IP traffic to the Logix controllers, and monitor for anomalous traffic patterns. If available, apply vendor firmware updates.

Recommended fix Moderate confidence

Latest firmware version available on Rockwell Automation PCDC for each controller (typically versions higher than 32.011 for 5480/5580 series and higher than 31.011 for 5380 series)

  1. 1. Identify the specific controller model (Compactlogix 5380, 5480, 5580, Guardlogix 5580, or Compact Guardlogix 5380) in your environment
  2. 2. Navigate to the Rockwell Automation Product Compatibility Download Center (PCDC) at https://compatibility.rockwellautomation.com/
  3. 3. Search for your specific controller model
  4. 4. Download the latest firmware version available for your controller
  5. 5. Review the release notes to confirm the firmware addresses CVE-2022-3752
  6. 6. Follow Rockwell Automation's standard firmware update procedure for Logix controllers
  7. 7. After updating, verify the controller is operational and test normal functionality
  8. 8. Document the firmware update for audit and compliance purposes
Caveat Firmware updates on industrial controllers may require user project file review/validation; ensure backup of project before update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Compactlogix 5480 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3752 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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