ABB HART Device DTM Vulnerability

OVERVIEW

Alexander Bolshev of Digital Security has identified an improper input vulnerability in the CodeWrights GmbH HART Device Type Manager (DTM) library used in ABB’s HART Device DTM. CodeWrights GmbH has addressed the vulnerability with a new library, which ABB have begun to integrate.

AFFECTED PRODUCTS

The following products use the vulnerable HART Device DTM library and are affected:

• ABB Third-Party Device Type Library, Version 1.17 and prior

• 800xA¾Device Management HART

• Freelance ABB Third-Party HART DTMLibrary, Version 1.4.178.214 and prior

• Freelance 800F

• S Plus Melody ABB Third-Party HART DTMLibrary, Version 1.4.175.185 and prior

• Symphony Plus with Composer Melody
• S+Engineering for Melody
• Composer Field

IMPACT

The vulnerability causes a buffer overflow in the HART Device DTM crashing the Field Device Tool (FDT) Frame Application. The Frame Application must then be restarted. The Frame Application is primarily used for remote configuration. Exploitation of this vulnerability does not result in loss of information, control, or view by the control system of the HART devices on the 4-20 mA HART Loop.

Impact to individual organizations depends on many factors that are unique to each organization. NCCIC/ICS-CERT recommends that organizations evaluate the impact of this vulnerability based on their operational environment, architecture, and product implementation.

BACKGROUND

ABB is a company based in Switzerland that maintains offices in several countries around the world. ABB develops products in multiple critical sectors that are deployed worldwide.

The affected product is the HART Device DTM library used by ABB HART-based field devices in the FDT/DTM Frame application. According to ABB, these products are deployed across multiple critical infrastructure sectors. ABB estimates that these products are used worldwide.

VULNERABILITY CHARACTERIZATION

VULNERABILITY OVERVIEW

Successful injection of specially crafted packets to the Device DTM causes a buffer overflow condition in the Frame Application. The FDT Frame Application becomes unresponsive, and the Device DTM stops functioning.

CVE-2014-9191NVD, http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9191, web site last accessed March 10, 2015. has been assigned to this vulnerability. A CVSS v2 base score of 1.8 has been assigned; the CVSS vector string is (AV:A/AC:H/Au:N/C:N/I:N/A:P).CVSS Calculator, http://nvd.nist.gov/cvss.cfm?version=2&vector=AV:A/AC:H/Au:N/C:N/I:N/A:P, web site last accessed March 10, 2015.

VULNERABILITY DETAILS

EXPLOITABILITY

This exploit on the FDT/DTM Frame Application is possible from any adjacent network that receives or passes packets from the HART Device DTM.

EXISTENCE OF EXPLOIT

No known public exploits specifically target this vulnerability.

DIFFICULTY

This is a complex vulnerability. Crafting a working exploit for this vulnerability would be difficult. Compromised access that allows access to the packets transmitted to Frame Application is required for exploitation. This exploit also requires a specific timing to crash the Frame Application. This increases the difficulty of a successful exploit.

MITIGATION

Recommended security practices and firewall configurations can help protect a process control network from attacks that originate from outside the network. Process control systems (including the 4-20 mA current loop for connecting field devices) should be physically protected from direct access by unauthorized personnel, have no direct connections to the Internet, and separated from other networks by means of a firewall system that has a minimal number of ports exposed. Process control systems should not be used for Internet surfing, instant messaging, or receiving emails. Portable computers and removable storage media should be carefully scanned for viruses before they are connected to a control system.

Using a virus scanner on all Windows-based system nodes, with the latest updates and with on‑access scanning enabled, can help prevent infection by malicious or unwanted software.

ABB’s security bulletin titled SECURITY BULLETIN - HART Vulnerability in ABB Third Party Device Type Library, includes patch information regarding this vulnerability. This security bulletin is available at:

http://www05.abb.com/global/scot/scot400.nsf/veritydisplay/8b6117ce372491c0c1257dea004c6536/$file/2PAA114210_-_en_SECURITY_BULLETIN_-_HART_Vulnerability_in_ABB_Third_Party_Device_Type_Library.pdf

ABB provides Alerts & Notifications of their products on their web site at:

http://www.abb.com/cawp/abbzh254/2c9d1261d9fa1dcfc1257950002e4fbf.aspx

ICS-CERT encourages asset owners to take additional defensive measures to protect against this and other cybersecurity risks.

• Minimize network exposure for all control system devices and/or systems, and ensure that they are not accessible from the Internet.
• Locate control system networks and remote devices behind firewalls, and isolate them from the business network.
• When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing that VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize that VPN is only as secure as the connected devices.

ICS-CERT also provides a section for control systems security recommended practices on the ICS-CERT web page at: http://ics-cert.us-cert.gov/content/recommended-practices. Several recommended practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies. ICS-CERT reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.

Additional mitigation guidance and recommended practices are publicly available in the ICS‑CERT Technical Information Paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies, that is available for download from the ICS-CERT web site (http://ics-cert.us-cert.gov/).

Organizations observing any suspected malicious activity should follow their established internal procedures and report their findings to ICS-CERT for tracking and correlation against other incidents.