Rockwell Fixes FactoryTalk Hole

Thursday, December 7, 2017 @ 02:12 PM gHale


Rockwell Automation has a new software release to mitigate an improper input validation vulnerability in its FactoryTalk Alarms and Events, according to a report with ICS-CERT.

Successful exploitation of this remotely exploitable vulnerability, which an unnamed major oil company discovered, may allow an attacker to cause a denial of service condition in the in the history archiver service running on FactoryTalk Alarms and Events.

RELATED STORIES
Hole Found in WAGO PLC
Siemens Mitigates Hole in Industrial Products
Siemens Updates Mitigation for KRACK Holes
Siemens Fixes SWT3000 Firmware

The following versions of FactoryTalk Alarms and Events, a component of the Factory Talk Services Platform, are affected:
• FactoryTalk Alarms and Events, Version 2.90 and earlier
FactoryTalk Alarms and Events sees use in the following Rockwell Automation products:
• FactoryTalk Services (RSLinx Enterprise), all versions
• FactoryTalk View SE, versions 5.00 and later
• Studio 5000 Logix Designer, versions 24 and later

No known public exploits specifically target this vulnerability. However, an attacker with low skill level could leverage the vulnerability.

An unauthenticated attacker with remote access to a network with FactoryTalk Alarms and Events can send a specially crafted set of packets packet to Port 403/TCP (the history archiver service), causing the service to either stall or terminate.

CVE-2017-14022 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.

The product mainly sees use in the chemical, critical manufacturing, food and agriculture, and water and wastewater systems sectors. It also sees action on a global basis.

Milwaukee, WI-based Rockwell Automation recommends upgrading to the latest version of FactoryTalk Alarms and Events, Version 2.90 or later, and applying available patches.

FactoryTalk Alarm and Event history is logged using the Rockwell Alarm Historian service using Port 403, writing alarms and events to the user-configured SQL Server database. If the Rockwell Automation Alarm Historian service is on the same machine as the Rockwell Alarm Event service, then Port 403 can be blocked remotely as the historical information is being logged to the local host rather than a remote host. Any other machine in the system that does not have the Rockwell Alarm Historian service on the same machine as the Rockwell Alarm Event service will require access to Port 403. However, FactoryTalk View SE clients using the Alarm and Event Log Viewer to view FactoryTalk Alarm and Event history do not require Port 403, and can thus be blocked.

Rockwell Automation recommends users who are unable to update and apply available patches should pursue risk mitigation strategies provided below. In addition, users are encouraged, when possible, to combine these strategies with the general security guidelines.
• Block all traffic to EtherNet/IP or other CIP protocol-based devices from outside the Manufacturing Zone by blocking or restricting access to TCP and UDP Port 2222 and Port 44818 using proper network infrastructure controls (such as firewalls), Unified Threat Management (UTM) devices, or other security appliances. For more information on TCP/UDP ports used by Rockwell Automation Products, see Knowledgebase Article ID 898270. Sign-in is required to access this Knowledgebase Article.

• Use trusted software, software patches, antivirus/antimalware programs, and interact only with trusted web sites and attachments.

Rockwell Automation’s security notification is available at the following URL with a valid account (sign-in required)



Leave a Reply

You must be logged in to post a comment.