Where
-Infinity
0
Severity
10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

An attacker with the ability to modify a user program may change user program code on some ControlLogix, CompactLogix, and GuardLogix Control systems. Studio 5000 Logix Designer writes user-readable program code to a separate location than the executed compiled code, allowing an attacker to change one and not the other.

Remedy

The following mitigations should be applied for ControlLogix 5560, ControlLogix 5570, ControlLogix 5580 series, GuardLogix 5570, GuardLogix 5580, GuardLogix 5380, CompactLogix, CompactLogix 5380 devices: Risk Mitigation A: Recompile and download user program code (i.e., acd). Put controller mode switch into Run position. If keeping controller mode switch in Run is impractical, use the following mitigation: Recompile and download user program code (i.e., acd). Monitor controller change log for any unexpected modifications or anomalous activity. Utilize the Controller Log feature. Utilize Change Detection in the Logix Designer Application. If available, use the functionality in FactoryTalk AssetCenter software to detect changes. Risk Mitigation B: Implement CIP Security to help prevent unauthorized connections when properly deployed. Supported controllers and communications modules include: ControlLogix 5580 processors using on-board EtherNet/IP port. GuardLogix 5580 processors using on-board EtherNet/IP port. ControlLogix 5580 processors operating in High Availability (HA) configurations using 1756-EN4TR ControlLogix 5560, ControlLogix 5570, ControlLogix 5580, GuardLogix 5570 and GuardLogix 5580 can use a 1756-EN4TR ControlLogix EtherNet/IP module. If using a 1756-EN2T, then replace with a 1756-EN4TR CompactLogix 5380 using on-board EtherNet/IP port. CompactLogix GuardLogix 5380 using on-board EtherNet/IP port. The following mitigations should be applied for 1768 CompactLogix, 1769 CompactLogix, CompactLogix 5370, and CompactLogix 5480 devices: Recompile and download user program code (i.e., acd). Put controller mode switch into Run position. If keeping controller mode switch in Run is impractical, then use the following mitigation: Recompile and download user program code (i.e., acd). Monitor controller change log for any unexpected modifications or anomalous activity. Use the Controller Log feature. Use Change Detection in the Logix Designer application. If available, use the functionality in FactoryTalk AssetCenter to detect changes.
First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203