dbcve.org
Compactlogix 5380 FirmwareOperating system · Rockwellautomation

CVE-2024-8626

HIGH · 7.5 CVSS v3.1 Published 2024-10-08
Fix available
A fix is available. Upgrade to 33.015 or later.
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
Due to a memory leak, a denial-of-service vulnerability exists in the Rockwell Automation affected products. A malicious actor could exploit this vulnerability by performing multiple actions on certain web pages of the product causing the affected products to become fully unavailable and require a power cycle to recover.

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 memory leak vulnerability in Rockwell Automation affected products allows remote attackers to cause denial of service by performing multiple actions on certain web pages, exhausting memory until the device becomes fully unresponsive and requires a physical power cycle to recover.

MitigationApply vendor patches when available; implement network segmentation and access controls to limit exposure to the web interface; consider deploying monitoring to detect memory exhaustion before complete failure.

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 5380 FirmwareOperating system
Affected:>= 33.011, < 33.015
Compact Guardlogix 5380 FirmwareOperating system
Affected:>= 33.011, < 33.015
Compactlogix 5480 FirmwareOperating system
Affected:>= 33.011, < 33.015
Controllogix 5580 FirmwareOperating system
Affected:>= 33.011, < 33.015
Guardlogix 5580 FirmwareOperating system
Affected:>= 33.011, < 33.015
1756 En4tr FirmwareOperating system
Affected:= 3.002

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 controller model and firmware version
    Open Studio 5000 Logix Designer or RSLinx Classic, locate the controller properties, and record the exact firmware revision number shown (for example, version 33.013). For 1756-EN4TR modules, check the module properties in the I/O configuration tree.
    Affected if The firmware version is 33.011, 33.012, 33.013, or 33.014 (any version >=33.011 and <33.015), or exactly 3.002 for the 1756-EN4TR module.
  2. Confirm web server is enabled
    In Studio 5000 Logix Designer, right-click the controller > Properties > Web Server tab, or access the controller's web interface via browser if network-accessible. Verify if the embedded web server is turned on.
    Affected if The web server feature is enabled on the controller, as the vulnerability is exploited through actions on certain web pages.
  3. Check controller memory status
    In Studio 5000, go to Controller Properties > Memory tab to view available memory. If the web interface is accessible, navigate to the Diagnostics or Status page to observe memory consumption over time.
    Affected if Memory usage shows abnormal consumption or depletion, or the controller reports low memory conditions, indicating active exploitation.
  4. Review network exposure of web interface
    Examine network configuration to determine if the controller's web server is reachable from untrusted networks. Check firewall rules, VLAN segmentation, or access lists that permit HTTP/HTTPS to the controller IP address.
    Affected if The web interface is exposed to broader networks beyond the operational technology segment, increasing exposure to remote attackers.

You are affected if your controller runs firmware version 33.011 through 33.014 (or 3.002 for 1756-EN4TR), the embedded web server is enabled, and the device is network-accessible to potential attackers.

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
Upgrade available Upgrade to 33.015 or later
Fixed in 33.015
Interim mitigation

Apply vendor patches when available; implement network segmentation and access controls to limit exposure to the web interface; consider deploying monitoring to detect memory exhaustion before complete failure.

Recommended fix High confidence

Firmware version 33.015 or later for Compactlogix 5380, Compact Guardlogix 5380, Compactlogix 5480, Controllogix 5580, Guardlogix 5580; contact Rockwell Automation for 1756 En4tr fix

  1. 1. Identify the affected device model and current firmware version using RSLinx Classic or Studio 5000 Logix Designer
  2. 2. Obtain the firmware update package from the official Rockwell Automation Product Compatibility and Download Center (PCDC) at https://compatibility.rockwellautomation.com/
  3. 3. Back up the controller project and configuration using the standard backup procedures in Studio 5000 Logix Designer
  4. 4. Use ControlFLASH Plus or ControlFLASH software to flash the firmware to version 33.015 or later
  5. 5. After firmware update completes, verify the controller is operational and connected via RSLinx Classic
  6. 6. Download the project back to the controller to ensure proper operation
  7. 7. Confirm the device is no longer exhibiting memory leak symptoms and responds to normal requests
Caveat Review release notes for any controller project changes required when moving to v33.x firmware; ensure backup before upgrade

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

Fix this in Compactlogix 5380 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8626 — 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-2024-8626 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