S4x19 — Miami — Programmable logic controllers (PLCs) long have been known to be easy marks for attack due to their blatant lack of built-in security, but a security researcher here this week will demonstrate how a hacker could commandeer some PLCs via their own advanced communications features.
Roee Stark, senior software engineer with ICS/SCADA network security monitoring firm Indegy, discovered that he could use two communication functions built into Rockwell Automation’s CompactLogix PLC line to wage network-borne attacks. Cybercriminals or nation-state actors could deploy these features as a way to stealthily infiltrate and control industrial processes and operations, or even reach into the target’s IT network infrastructure, he says.
Most PLC security research to date has focused ways to hack into PLCs or rig them with malware, for example, to alter the industrial process or compromise the devices’ ladder logic, basically the programming language used to code PLCs. Researchers have built rootkits and worms for PLCs, for example.
But Stark’s PLC hacking research instead targets the connectivity of a PLC. The PLCs openly allow connections to the network, he says, a design that leaves them open to network-based attacks. “It’s much easier than changing the programming of a controller, or making [a device] explode.”
The first of the two features he coupled together to exploit the PLCs is the so-called complex path feature, which comes with Rockwell CompactLogix PLCs that use the Common Industrial Protocol (CIP), a communication architecture for industrial networks that integrates those operations with IT-based networks and the Internet. CIP runs on EtherNet/IP, Control/Net, and other popular industrial network protocols.
Complex path lets you create a CIP session between two PLCs that aren’t directly connected: “So if PLC A is connected to PLC B, [which is then] connected to PLC C, you can create a connection from PLC A to C” via a path through PLC B, Stark explains. The feature allows you to forward and transfer messages from one PLC to another.
The second feature is the so-called socket object, which lets the PLC send and receive TCP or UDP traffic.
“When combining these two capabilities, we can send and receive packets from a controller we have access to and all other controllers that are connected to it – regardless of the connection type,” Stark says.
An attacker with direct or remote access to the Rockwell PLC could abuse those features to collect data for reconnaissance purposes; to exfiltrate data; and to further attack the network using known security vulnerabilities, for example.
If an attacker can reach the PLC on the plant floor either via the local network or the Internet, he or she can then spot the ControlNet connection and employ the complex path feature to reach other controllers in the plant, he explains. Once he or she reaches the PLC, they can collect data via the socket interface using queries and running scans.
Stark doesn’t know for sure if these attacks could also work on other vendors’ PLCs since he hasn’t tested them. Even so, he notes, Rockwell’s CompactLogix series contains more advanced communications protocols and features than most PLCs, he says. “As far as I know, these features are fairly unique to them,” he says of the PLC communications features.
Indegy did not disclose the research to Rockwell since it wasn’t a pure vulnerability disclosure, but rather a way to abuse the controller’s features, Stark says. “It’s not a vulnerability because you don’t bypass anything and you don’t exploit any control,” he says. “The programmatic flow is doing exactly what it is supposed to do” when you abuse it, he notes.
A Rockwell Automation spokesperson declined to comment on Indegy’s research when contacted by Dark Reading.
The Rockwell PLCs actually come with a logging feature that would be useful for catching such attacks, but logging is disabled by default in the devices, Stark found. “And turning it on again would not be trivial … you have to dig deep into the Web interface to find it,” he says.
Authentication would help thwart such an attack as well, but the PLCs don’t include such a feature, he says, and continuous network monitoring – a technology Indegy sells – could help spot any nefarious network activity using the legitimate PLC communications features in the Rockwell devices. Route whitelists also could prevent unauthorized PLC traffic.
Meanwhile, the focus on securing PLCs on the plant floor traditionally has been mostly on protecting them from malicious firmware updates, or from getting infected with malware. “They usually only take into account the execution flow,” Stark says.
Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise … View Full Bio