dbcve.org
Micrologix 1400 B FirmwareOperating system · Rockwellautomation

CVE-2017-14473

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-05
Fix available
A fix is available. Upgrade to after 21.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 exploitable access control vulnerability exists in the data, program, and function file permissions functionality of Allen Bradley Micrologix 1400 Series B FRN 21.2 and before. A specially crafted packet can cause a read or write operation resulting in disclosure of sensitive information, modification of settings, or modification of ladder logic. An attacker can send unauthenticated packets to trigger this vulnerability. Required Keyswitch State: Any Description: Reads the encoded ladder logic from its data file and print it out in HEX.

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

A detailed technical summary for this CVE is being prepared.

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
Micrologix 1400 B FirmwareOperating system
Affected:<= 21.2

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 a release after 21.2
Recommended fix Moderate confidence

Contact Rockwell Automation for the latest fixed firmware version (firmware > 21.2)

  1. 1. Identify the current firmware version of the Micrologix 1400 Series B PLC by accessing the device through RSLogix 500 or the device's LCD interface.
  2. 2. Contact Rockwell Automation technical support or visit their official website to obtain the latest firmware version for the Micrologix 1400 Series B.
  3. 3. Download the firmware update package from the official Rockwell Automation download site (https://www.rockwellautomation.com/).
  4. 4. Use the appropriate firmware update tool (such as Firmware Supervisor or similar Rockwell-provided utility) to upload the new firmware to the device.
  5. 5. Follow the manufacturer's firmware update instructions carefully, ensuring stable power to the device during the update process.
  6. 6. After updating, verify the new firmware version matches the fixed release.
  7. 7. If upgrading is not immediately possible, implement network segmentation to isolate the PLC from untrusted networks and implement firewall rules to restrict access to authorized IP addresses only.
Caveat ICS/OT firmware upgrades may require validation in a test environment before production deployment to ensure compatibility with existing control programs

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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