CVE-2014-5410
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 · uneditedThe DNP3 feature on Rockwell Automation Allen-Bradley MicroLogix 1400 1766-Lxxxxx A FRN controllers 7 and earlier and 1400 1766-Lxxxxx B FRN controllers before 15.001 allows remote attackers to cause a denial of service (process disruption) via malformed packets over (1) an Ethernet network or (2) a serial line.
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 confidenceThe DNP3 protocol implementation in Rockwell Automation MicroLogix 1400 controllers (versions A FRN 7 and earlier, B FRN before 15.001) contains a vulnerability where malformed packets sent over Ethernet or serial connections can cause the device to become unresponsive, disrupting control processes.
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= 1400CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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.
-
Confirm device modelIdentify the target device to verify it is a Rockwell Automation MicroLogix 1400 controller (check device labeling, firmware metadata, or management interface)Affected if Device is not a MicroLogix 1400 controller - vulnerability does not apply
-
Check installed firmware versionRetrieve the current firmware revision number from the controller (via RSLogix, RSLinx, device web interface, or LCD menu). Look for FRN (Firmware Revision Number) designation.Affected if Firmware is A FRN 7 or earlier, OR B FRN before 15.001 - these versions contain the vulnerable DNP3 implementation
-
Verify DNP3 protocol is enabledExamine controller configuration for DNP3 protocol settings (typically found in communication or protocol configuration menus in RSLogix or the device web interface)Affected if DNP3 protocol is enabled and configured on the controller - this is required for the malformed packet flaw to be triggered
-
Check DNP3 network exposureIdentify if DNP3 ports (default UDP/TCP 20000) are accessible on the controller and whether the controller is reachable from network segments outside the control system trust boundaryAffected if DNP3 protocol is exposed to untrusted or external network segments, increasing attack likelihood
You are affected if you have a MicroLogix 1400 controller with firmware A FRN 7 or earlier or B FRN before 15.001, and DNP3 protocol is enabled and accessible on your 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 dataUpgrade controller firmware to version B FRN 15.001 or later. Additionally, network segmentation and firewall rules should restrict unauthorized access to the DNP3 ports on critical control networks.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5410 — 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-2014-5410 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