dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-7567

MEDIUM · 6.9 CVSS v4.0 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
A denial-of-service vulnerability exists via the CIP/Modbus port in the Rockwell Automation Micro850/870 (2080 -L50E/2080 -L70E). If exploited, the CIP/Modbus communication may be disrupted for short duration.

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 denial-of-service vulnerability exists in the CIP/Modbus communication port of Rockwell Automation Micro850 and Micro870 programmable logic controllers (2080-L50E and 2080-L70E). If exploited, the vulnerability can disrupt CIP/Modbus communications for a short duration.

MitigationApply available firmware updates from Rockwell Automation. Until then, restrict network access to CIP/Modbus ports through network segmentation and firewalls, and monitor industrial protocol traffic for anomalous patterns indicative of DoS attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 PLC model
    Locate the physical PLC or check asset inventory for Rockwell Automation Micro850 (2080-L50E) or Micro870 (2080-L70E) controllers
    Affected if The device is a Micro850 or Micro870 controller, specifically models 2080-L50E or 2080-L70E
  2. Check firmware version
    Access the controller via RSLogix 5000/Studio 5000 or check the firmware version through the controller's properties or boot prompt
    Affected if The installed firmware version falls within the affected version range (compare your version to the officially listed affected versions for this CVE)
  3. Verify CIP port status
    Check if the CIP (Common Industrial Protocol) port (typically port 44818) is enabled and configured on the controller through RSLogix or controller properties
    Affected if CIP communication is enabled on the controller - this is required for the vulnerability to be exploitable
  4. Verify Modbus TCP port status
    Check if Modbus TCP is enabled in the controller configuration through the communication settings in the programming software
    Affected if Modbus TCP is enabled on the controller - this is an additional attack vector for this vulnerability
  5. Assess network exposure
    Review firewall rules, network segments, and ACLs to determine if the CIP/Modbus ports are accessible from untrusted network segments or external networks
    Affected if CIP (port 44818) or Modbus TCP (port 502) ports are accessible from untrusted or external network segments

A user is affected if they operate Micro850 or Micro870 PLCs (2080-L50E/2080-L70E) with a vulnerable firmware version that has CIP and/or Modbus ports enabled and exposed to potentially untrusted network access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available firmware updates from Rockwell Automation. Until then, restrict network access to CIP/Modbus ports through network segmentation and firewalls, and monitor industrial protocol traffic for anomalous patterns indicative of DoS attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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