Rockwell Automation Logix Controllers (Update A)

Risk Summary

Successful exploitation of this vulnerability could allow a remote unauthenticated attacker to bypass the verification mechanism and connect with Logix controllers. Additionally, this vulnerability could enable an unauthorized third-party tool to alter the controller 's configuration and/or application code.

CVEs (1)

Remediations

• Rockwell Automation has determined this vulnerability cannot be mitigated with a patch. Rockwell encourages users to combine its specific risk mitigation recommendations with general security guidelines for a comprehensive defense-in-depth strategy.
• A comprehensive defense-in-depth strategy can reduce the risk of this vulnerability. To reduce risk, Rockwell recommends users ensure they are employing proper network segmentation and security controls
• Minimizing network exposure for all control system devices and/or systems and confirm these devices are not accessible from the Internet.
• Locating control system networks and devices behind firewalls and isolating them from the enterprise/business network.
• Restricting or blocking traffic on TCP 44818 from outside of the industrial control system network zone. For more information on the TCP/UDP ports used by Rockwell Automation products, see BF7490 (login required).
• When remote access is required, use secure methods such as virtual private networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. VPN is only as secure as the connected devices.
• Users should refer to the Converged Plantwide Ethernet (CPwE) Design and Implementation Guide for best practices for deploying network segmentation, as well as broader defense-in-depth strategies. Users can also refer to Rockwell Automation's System Security Design Guidelines on how to use Rockwell Automation products to improve the security of industrial automation systems.
• Common Industrial Protocol (CIP) Security mitigates this vulnerability as it provides the ability to deploy TLS- and DTLS-based secure communications to supported products. CIP Security is an enhancement to the ODVA (Open DeviceNet Vendors Association) EtherNet/IP industrial communication standard and directly addresses this vulnerability. CIP Security allows users to leverage and manage certificates and/or pre-shared keys, and does not make use of any hardcoded keys.
• Users requiring setup or deployment guidance for CIP Security protocol should refer to the CIP Security deployment reference guide.
• Additionally, Rockwell recommends users follow the following risk mitigation and recommended user actions
• ControlLogix 5580 v32 or later: Put controller's mode switch to “Run” mode. If the above cannot be deployed the followings mitigations are recommended: Deploy CIP Security for Logix Designer connections through the front port. CIP Security prevents unauthorized connection when deployed properly. If not using the front port use a 1756-EN4TR ControlLogix Ethernet/IP Module and deploy CIP Security. The 1756-EN4TR supports CIP Security which prevents unauthorized connections when properly deployed.
• Deploy CIP Security for Logix Designer connections through the front port. CIP Security prevents unauthorized connection when deployed properly.
• If not using the front port, use a 1756-EN4TR ControlLogix Ethernet/IP Module and deploy CIP Security. The 1756-EN4TR supports CIP Security which prevents unauthorized connections when properly deployed.
• ControlLogix 5580 v31: Put controller's mode switch to “Run” mode. If the above cannot be deployed the following mitigations are recommended: Apply v32 or later and follow mitigations actions outlined above. If unable to apply a newer version, use a 1756-EN4TR ControlLogix EtherNet/IP Module and deploy CIP Security. The 1756-EN4TR supports CIP Security, which prevents unauthorized connections when properly deployed.
• ControlLogix 5570 v31 or later: Put controller's mode switch to “Run” mode. If the above cannot be deployed the following mitigations are recommended: Use a 1756-EN4TR ControlLogix EtherNet/IP Module and deploy CIP Security. The 1756-EN4TR supports CIP Security, which prevents unauthorized connections when properly deployed.
• Use a 1756-EN4TR ControlLogix EtherNet/IP Module and deploy CIP Security. The 1756-EN4TR supports CIP Security, which prevents unauthorized connections when properly deployed.
• ControlLogix 5580 v28-v30, ControlLogix 5570 v18 or later, ControlLogix 5560 v16 or later, ControlLogix 5550 v16, GuardLogix 5580 v31 or later, GuardLogix 5570 v20 or later, GuardLogix 5560 v16 or later, 1768 CompactLogix v16 or later, 1769 CompactLogix v16 or later, CompactLogix 5370 v20 or later, CompactLogix 5380 v28 or later, CompactLogix 5480 v32 or later, Compact GuardLogix 5370 v28 or later, Compact GuardLogix 5380 v31 or later, FlexLogix 1794-L34 v16, DriveLogix 5370 v16 or later. Put controller's mode switch to “Run” mode.
• SoftLogix 5800: No additional mitigation available. Follow the Converged Plantwide Ethernet (CPwE) Design and Implementation Guide.
• Monitor controller change log for any unexpected modifications or anomalous activity.
• If using v17 or later, utilize the Controller Log feature.
• If using v20 or later, utilize Change Detection in the Logix Designer Application.
• If available, use the functionality in Factory Talk AssetCentre to detect changes.
• Rockwell Automation has published a security advisory that further describes how this vulnerability affects the Studio 5000 Logix Designer software and associated controllers.
• Requests for additional information can be sent to the Rockwell RASecure Inbox ([email protected]).

Affected Vendors

Affected Products (3)

Affected Sectors

Multiple