CVE-2024-21916
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 denial-of-service vulnerability exists in specific Rockwell Automation ControlLogix ang GuardLogix controllers. If exploited, the product could potentially experience a major nonrecoverable fault (MNRF). The device will restart itself to recover from the MNRF.
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 denial-of-service vulnerability exists in specific Rockwell Automation ControlLogix and GuardLogix controllers. If exploited, the vulnerability can trigger a major nonrecoverable fault (MNRF), causing the affected controller to restart automatically to recover.
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.011= 20.011= 20.054_kit1CVSS 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 the controller modelConnect to the controller via RSLogix 5000/Studio 5000 or check the physical controller hardware label to determine if it is a ControlLogix 5570 or GuardLogix 5570 controllerAffected if Controller model is ControlLogix 5570 or GuardLogix 5570 (non-5570 models are not affected)
-
Retrieve the firmware versionIn Studio 5000 or RSLogix 5000, right-click the controller in the Controller Organizer and select 'Properties'. View the 'Revision' field which shows the firmware version (e.g., 20.011). For redundant controllers, check both the primary and backup modules.Affected if Firmware version cannot be retrieved or does not match the listed versions - if you cannot determine the version, treat as potentially affected
-
Compare firmware version to affected rangesMatch the retrieved firmware version against: ControlLogix 5570 = 20.011, GuardLogix 5570 = 20.011, ControlLogix 5570 Redundant = 20.054_kit1Affected if The installed firmware version exactly matches 20.011 (ControlLogix or GuardLogix 5570) or 20.054_kit1 (ControlLogix 5570 Redundant)
-
Check for MNRF fault symptomsReview the controller's fault log in Studio 5000 by going to 'Controller Tags' > 'Controller Faults' or checking the event log for 'Major Nonrecoverable Fault' entries and unexpected automatic restartsAffected if Recent fault history shows MNRF events or unexplained automatic controller restarts, especially if multiple occurrences are logged in a short timeframe
Your environment is affected if you have a ControlLogix 5570 or GuardLogix 5570 controller running firmware version 20.011, or a ControlLogix 5570 Redundant controller running firmware version 20.054_kit1.
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 dataApply vendor-provided patches or firmware updates to affected ControlLogix and GuardLogix controllers; implement network segmentation and access controls to reduce exposure until remediation is possible.
- 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-2024-21916 — 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-2024-21916 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