{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"1756-ENBT, 1756-EWEB, 1768-ENBT, 1768-EWEB communication modules","vendor":"Rockwell Automation","versions":[{"status":"affected","version":"All"}]},{"defaultStatus":"unaffected","product":"CompactLogix L32E and L35E controllers","vendor":"Rockwell Automation","versions":[{"status":"affected","version":"All"}]},{"defaultStatus":"unaffected","product":"1788-ENBT FLEXLogix adapter","vendor":"Rockwell Automation","versions":[{"status":"affected","version":"All"}]},{"defaultStatus":"unaffected","product":"1794-AENTR FLEX I/O EtherNet/IP adapter","vendor":"Rockwell Automation","versions":[{"status":"affected","version":"All"}]},{"defaultStatus":"unaffected","product":"ControlLogix, CompactLogix, GuardLogix, and SoftLogix","vendor":"Rockwell Automation","versions":[{"lessThanOrEqual":"18","status":"affected","version":"0","versionType":"custom"}]},{"defaultStatus":"unaffected","product":"CompactLogix and SoftLogix controllers","vendor":"Rockwell Automation","versions":[{"lessThanOrEqual":"19","status":"affected","version":"0","versionType":"custom"}]},{"defaultStatus":"unaffected","product":"ControlLogix and GuardLogix controllers","vendor":"Rockwell Automation","versions":[{"lessThanOrEqual":"20","status":"affected","version":"0","versionType":"custom"}]},{"defaultStatus":"unaffected","product":"MicroLogix","vendor":"Rockwell Automation","versions":[{"status":"affected","version":"1100"},{"status":"affected","version":"1400"}]}],"credits":[{"lang":"en","type":"finder","value":"Rubén Santamarta of IOActive identified vulnerabilities in Rockwell Automation’s ControlLogix PLC and released proof-of-concept (exploit) code at the Digital Bond S4 Conference on January 19, 2012."}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"

\nWhen an affected \nproduct receives a valid CIP message from an unauthorized or unintended \nsource to Port 2222/TCP, Port 2222/UDP, Port 44818/TCP, or Port \n44818/UDP that changes the product’s configuration and network \nparameters, a DoS condition can occur. This situation could cause loss \nof availability and a disruption of communication with other connected \ndevices. 

Rockwell Automation EtherNet/IP products; 1756-ENBT, 1756-EWEB, 1768-ENBT, and 1768-EWEB communication modules; CompactLogix L32E and L35E controllers; 1788-ENBT FLEXLogix adapter; 1794-AENTR FLEX I/O EtherNet/IP adapter; ControlLogix 18 and earlier; CompactLogix 18 and earlier; GuardLogix 18 and earlier; SoftLogix 18 and earlier; CompactLogix controllers 19 and earlier; SoftLogix controllers 19 and earlier; ControlLogix controllers 20 and earlier; GuardLogix controllers 20 and earlier; and MicroLogix 1100 and 1400 

"}],"value":"When an affected \nproduct receives a valid CIP message from an unauthorized or unintended \nsource to Port 2222/TCP, Port 2222/UDP, Port 44818/TCP, or Port \n44818/UDP that changes the product’s configuration and network \nparameters, a DoS condition can occur. This situation could cause loss \nof availability and a disruption of communication with other connected \ndevices. \n\nRockwell Automation EtherNet/IP products; 1756-ENBT, 1756-EWEB, 1768-ENBT, and 1768-EWEB communication modules; CompactLogix L32E and L35E controllers; 1788-ENBT FLEXLogix adapter; 1794-AENTR FLEX I/O EtherNet/IP adapter; ControlLogix 18 and earlier; CompactLogix 18 and earlier; GuardLogix 18 and earlier; SoftLogix 18 and earlier; CompactLogix controllers 19 and earlier; SoftLogix controllers 19 and earlier; ControlLogix controllers 20 and earlier; GuardLogix controllers 20 and earlier; and MicroLogix 1100 and 1400"}],"metrics":[{"cvssV2_0":{"accessComplexity":"LOW","accessVector":"NETWORK","authentication":"NONE","availabilityImpact":"COMPLETE","baseScore":8.5,"confidentialityImpact":"NONE","integrityImpact":"PARTIAL","vectorString":"AV:N/AC:L/Au:N/C:N/I:P/A:C","version":"2.0"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-284","description":"CWE-284","lang":"en","type":"CWE"}]}],"providerMetadata":{"orgId":"7d14cffa-0d7d-4270-9dc0-52cabd5a23a6","shortName":"icscert","dateUpdated":"2025-06-30T21:33:10.902Z"},"references":[{"tags":["x_refsource_MISC"],"url":"http://www.us-cert.gov/control_systems/pdf/ICSA-13-011-03.pdf"},{"url":"https://rockwellautomation.custhelp.com/app/answers/detail/a_id/470154"},{"url":"https://rockwellautomation.custhelp.com/app/answers/detail/aid/470155"},{"url":"https://rockwellautomation.custhelp.com/app/answers/detail/aid/470156"},{"url":"http://rockwellautomation.custhelp.com/app/answers/detail/a_id/54102"}],"solutions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"

According to Rockwell, any of the above products that become affected by a vulnerability can be reset by rebooting or power cycling the affected product. After the reboot, the affected product may require some reconfiguration.

To mitigate the vulnerabilities, Rockwell has developed and released security patches on July 18, 2012, to address each of the issues. To download and install the patches please refer to Rockwell’s Advisories at:

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/470154
https://rockwellautomation.custhelp.com/app/answers/detail/aid/470155
https://rockwellautomation.custhelp.com/app/answers/detail/aid/470156

For more information on security with Rockwell Automation products, please refer to Rockwell’s Security Advisory Index.


"}],"value":"According to Rockwell, any of the above products that become affected by a vulnerability can be reset by rebooting or power cycling the affected product. After the reboot, the affected product may require some reconfiguration.\n\nTo mitigate the vulnerabilities, Rockwell has developed and released security patches on July 18, 2012, to address each of the issues. To download and install the patches please refer to Rockwell’s Advisories at:\n\n https://rockwellautomation.custhelp.com/app/answers/detail/a_id/470154 \n https://rockwellautomation.custhelp.com/app/answers/detail/aid/470155 \n https://rockwellautomation.custhelp.com/app/answers/detail/aid/470156 \n\nFor more information on security with Rockwell Automation products, please refer to Rockwell’s Security Advisory Index http://rockwellautomation.custhelp.com/app/answers/detail/a_id/54102 ."}],"source":{"advisory":"ICSA-13-011-03","discovery":"EXTERNAL"},"title":"Rockwell Automation ControlLogix PLC Improper Access Control","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"

Rockwell recommends updating to the newest firmware patches to fix the vulnerabilities, but if not able to do so right away, then Rockwell advises immediately employing the following mitigations for each of the affected products.

To mitigate the vulnerabilities pertaining to receiving valid CIP packets:

  1. Block all traffic to the Ethernet/IP or other CIP protocol-based devices from outside the Manufacturing Zone by restricting or blocking access to TCP and UDP Ports 2222 and 44818 using appropriate security technology such as a firewall or Unified Threat Management (UTM).
  2. Employ a UTM appliance that specifically supports CIP message filtering.
\n\n

In addition to the above, Rockwell recommends concerned customers remain vigilant and continue to follow security strategies that help reduce risk and enhance overall control system security. Where possible, they suggest you apply multiple recommendations and complement this list with your own best-practices:

  1. Employ layered security and defense-in-depth methods in system design to restrict and control access to individual products and control networks. Refer to http://www.ab.com/networks/architectures.html for comprehensive information about implementing validated architectures designed to deliver these measures.
  2. Restrict physical and electronic access to automation products, networks, and systems to only those individuals authorized to be in contact with control system equipment.
  3. Employ firewalls with ingress/egress filtering, intrusion detection/prevention systems, and validate all configurations. Evaluate firewall configurations to ensure other appropriate inbound and outbound traffic is blocked.
  4. Use up-to-date end-point protection software (e.g., antivirus/antimalware software) on all PC-based assets.
  5. Make sure that software and control system device firmware is patched to current releases.
  6. Periodically change passwords in control system components and infrastructure devices.
  7. Where applicable, set the controller key-switch/mode-switch to RUN mode.
\n\n\n\nFor more information on security with Rockwell Automation products, please refer to Rockwell’s Security Advisory Index.\n\n
"}],"value":"Rockwell recommends updating to the newest firmware patches to fix the vulnerabilities, but if not able to do so right away, then Rockwell advises immediately employing the following mitigations for each of the affected products.\n\nTo mitigate the vulnerabilities pertaining to receiving valid CIP packets:\n\n * Block all traffic to the Ethernet/IP or other CIP protocol-based devices from outside the Manufacturing Zone by restricting or blocking access to TCP and UDP Ports 2222 and 44818 using appropriate security technology such as a firewall or Unified Threat Management (UTM).\n * Employ a UTM appliance that specifically supports CIP message filtering.\n\n\nIn addition to the above, Rockwell recommends concerned customers remain vigilant and continue to follow security strategies that help reduce risk and enhance overall control system security. Where possible, they suggest you apply multiple recommendations and complement this list with your own best-practices:\n\n * Employ layered security and defense-in-depth methods in system design to restrict and control access to individual products and control networks. Refer to http://www.ab.com/networks/architectures.html for comprehensive information about implementing validated architectures designed to deliver these measures.\n * Restrict physical and electronic access to automation products, networks, and systems to only those individuals authorized to be in contact with control system equipment.\n * Employ firewalls with ingress/egress filtering, intrusion detection/prevention systems, and validate all configurations. Evaluate firewall configurations to ensure other appropriate inbound and outbound traffic is blocked.\n * Use up-to-date end-point protection software (e.g., antivirus/antimalware software) on all PC-based assets.\n * Make sure that software and control system device firmware is patched to current releases.\n * Periodically change passwords in control system components and infrastructure devices.\n * Where applicable, set the controller key-switch/mode-switch to RUN mode.\n\n\n\n\nFor more information on security with Rockwell Automation products, please refer to Rockwell’s Security Advisory Index http://rockwellautomation.custhelp.com/app/answers/detail/a_id/54102 ."}],"x_generator":{"engine":"Vulnogram 0.2.0"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"ics-cert@hq.dhs.gov","ID":"CVE-2012-6439","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"Rockwell Automation EtherNet/IP products; 1756-ENBT, 1756-EWEB, 1768-ENBT, and 1768-EWEB communication modules; CompactLogix L32E and L35E controllers; 1788-ENBT FLEXLogix adapter; 1794-AENTR FLEX I/O EtherNet/IP adapter; ControlLogix 18 and earlier; CompactLogix 18 and earlier; GuardLogix 18 and earlier; SoftLogix 18 and earlier; CompactLogix controllers 19 and earlier; SoftLogix controllers 19 and earlier; ControlLogix controllers 20 and earlier; GuardLogix controllers 20 and earlier; and MicroLogix 1100 and 1400 allow remote attackers to cause a denial of service (control and communication outage) via a CIP message that modifies the (1) configuration or (2) network parameters."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"http://www.us-cert.gov/control_systems/pdf/ICSA-13-011-03.pdf","refsource":"MISC","url":"http://www.us-cert.gov/control_systems/pdf/ICSA-13-011-03.pdf"}]}}},"adp":[{"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2024-08-06T21:28:39.816Z"},"title":"CVE Program Container","references":[{"tags":["x_refsource_MISC","x_transferred"],"url":"http://www.us-cert.gov/control_systems/pdf/ICSA-13-011-03.pdf"}]}]},"cveMetadata":{"assignerOrgId":"7d14cffa-0d7d-4270-9dc0-52cabd5a23a6","assignerShortName":"icscert","cveId":"CVE-2012-6439","datePublished":"2013-01-24T21:00:00.000Z","dateReserved":"2012-12-26T00:00:00.000Z","dateUpdated":"2025-06-30T21:33:10.902Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.1"}