dbcve.org
Softlogix 5800 Controller FirmwareOperating system · Rockwellautomation

CVE-2016-9343

CRITICAL · 10.0 CVSS v3.1 Published 2017-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 issue was discovered in Rockwell Automation Logix5000 Programmable Automation Controller FRN 16.00 through 21.00 (excluding all firmware versions prior to FRN 16.00, which are not affected). By sending malformed common industrial protocol (CIP) packet, an attacker may be able to overflow a stack-based buffer and execute code on the controller or initiate a nonrecoverable fault resulting in a denial of service.

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 · high confidence

Stack-based buffer overflow vulnerability in Rockwell Automation Logix5000 PAC firmware versions FRN 16.00-21.00. Exploitable via malformed Common Industrial Protocol (CIP) packets, allowing remote code execution or causing a nonrecoverable fault resulting in denial of service.

MitigationApply vendor-supplied firmware update to remediate the vulnerability. For production environments, develop and test update procedures in a staging environment before deploying, and ensure rollback capabilities are in place.

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
Softlogix 5800 Controller FirmwareOperating system
Affected:= 18.00= 19.00= 20.00= 21.00
Rslogix Emulate 5000 FirmwareOperating system
Affected:= 18.00= 19.00= 20.00= 21.00
Guardlogix 5570 Controller FirmwareOperating system
Affected:= 16.00= 17.00= 18.00= 19.00= 20.00= 20.010= 20.017= 21.00
Flexlogix L34 Controller FirmwareOperating system
Affected:= 16.00
Controllogix L55 Controller FirmwareOperating system
Affected:= 16.00= 16.020= 16.022
Controllogix 5570 Redundant Controller FirmwareOperating system
Affected:= 20.00= 20.050= 20.055= 21.00
Controllogix 5570 Controller FirmwareOperating system
Affected:= 18.00= 19.00= 20.010= 20.013= 21.00
Controllogix 5560 Redundant Controller FirmwareOperating system
Affected:= 16.00= 19.00= 20.00= 20.050= 20.055

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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
    Access the controller through RSLinx Classic or FactoryTalk View. Navigate to the controller properties or system properties to view the firmware revision (FRN) number. Alternatively, use the 'Who Active' window in RSLinx to browse the network and view device properties.
    Affected if The controller model matches any of the affected products (Softlogix 5800, Rslogix Emulate 5000, Guardlogix 5570, Flexlogix L34, Controllogix L55, Controllogix 5570 Redundant, Controllogix 5570, Controllogix 5560 Redundant) AND the firmware version matches one of the listed vulnerable versions (16.0
  2. Verify CIP communication is enabled
    Check if Common Industrial Protocol (CIP) communication is enabled on the controller. In RSLinx, verify the driver configuration includes Ethernet/IP or CIP devices. Inspect controller properties in RSLogix 5000/Studio 5000 to confirm CIP connections are allowed.
    Affected if CIP communication is enabled and the controller is accessible over Ethernet/IP, as this is the required attack vector for the malformed CIP packets.
  3. Assess network exposure of controller
    Review network topology and firewall rules to determine if the controller's Ethernet/IP port (typically port 44818) is accessible from external networks or untrusted zones. Check if the controller is directly connected to a corporate network rather than an isolated industrial DMZ.
    Affected if The controller's CIP/Ethernet/IP port is accessible from untrusted networks, increasing the likelihood of remote exploitation.
  4. Check for recent connection logs or anomalous CIP traffic
    Review RSLinx communication diagnostics, controller event logs, or network monitoring tools for unusual CIP packet patterns or connection attempts. Look for entries indicating malformed CIP requests or nonrecoverable faults.
    Affected if There are logged incidents of malformed CIP packets, unexpected controller faults, or unusual CIP connection attempts.

The environment is affected if any Logix5000 controller (Softlogix 5800, Rslogix Emulate 5000, Guardlogix 5570, Flexlogix L34, Controllogix L55, Controllogix 5570, or Controllogix 5560) is running firmware versions within the listed vulnerable FRN ranges AND has CIP/Ethernet/IP communication enabled and accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware update to remediate the vulnerability. For production environments, develop and test update procedures in a staging environment before deploying, and ensure rollback capabilities are in place.

Recommended fix High confidence

Firmware FRN 21.00 or later (controller-specific fixed releases available from Rockwell Automation)

  1. 1. Identify the exact controller model and current firmware version from the affected product list (Softlogix 5800, Rslogix Emulate 5000, Guardlogix 5570, Flexlogix L34, Controllogix L55, Controllogix 5570, Controllogix 5560 Redundant)
  2. 2. Access the Rockwell Automation Product Change Notices (PCN) or security advisories at https://www.rockwellautomation.com/resources/rockwell-automation-website/pages/our-products-and-services/technologies/security-and-resilience.aspx
  3. 3. Download the firmware update for your specific controller model that resolves this vulnerability (FRN 21.00 and later contain the fix)
  4. 4. Follow Rockwell Automation's firmware update procedures - typically requires connecting via RSLinx Classic or FactoryTalk Gateway
  5. 5. Backup the controller project using RSLogix 5000/Studio 5000 before performing firmware update
  6. 6. Update firmware through Rockwell's ControlFLASH or ControlFLASH Plus utility
  7. 7. Verify the controller returns to Run mode and project loads correctly after update
  8. 8. Confirm the new firmware version is at or above the fixed release (FRN 21.00 or later for your controller)
Caveat Firmware updates on industrial controllers may require project compatibility verification; backup project before upgrading

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

Fix this in Softlogix 5800 Controller Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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