Vulnerabilities / Threats
11/10/2011
01:09 PM
50%
50%

Prisons May Be Vulnerable To Stuxnet-Style Attack

Researchers found easy-to-write malware could subvert prison control systems, cause spontaneous opening of all cell doors.

It's Christmas Eve in a maximum security prison, when all of the cell doors on death row simultaneously open without warning. What happened? That was the question posed by the warden of a prison in which that exact scenario occurred.

At last month's Hacker Halted Conference in Miami, the group formed to answer that question presented the results of its research into "SCADA and PLC Vulnerabilities in Correctional Facilities." In short, they discovered that there are numerous vulnerabilities in the industrial control--often referred to as supervisory control and data acquisition, aka SCADA--systems and programmable logic controllers (PLCs) used in today's modern and highly automated prisons, which could be remotely exploited to compromise such systems.

"Using the PLC's own software library, we were able to not only unlock any door in the prison system, but we could also send false status signals back to central and/or housing control reporting that the door is closed and locked," said researcher John Strauchs on his blog. "Our results were far better than we expected." Furthermore, the team said that acquiring the hardware and software required for its research cost only $2,500, although by not bothering to pay for legitimate software licenses, that cost could have been reduced to about $500.

[Concerned about shoring up your systems against Stuxnet-style attacks? Learn 5 Things To Do To Defend Against Duqu.]

The group of researchers was composed of Strauchs, a former CIA operations officer who's conducted security engineering or consulting for more than 114 justice industry design projects, including 14 federal prisons, 23 state prisons, and 27 city or county jails; Tiffany Rad, the president of ELCnetworks; and Teague Newman, a Washington-based information security consultant with experience in penetration testing.

A Federal Bureau of Prisons spokesman this week said that the agency is "aware of this research and taking it very seriously," according to The Washington Times. Likewise, the research team said it's been working with multiple manufacturers and government agencies to identify current vulnerabilities and craft workarounds.

Of course, security experts have been warning about these types of control system vulnerabilities for years. But it wasn't until Stuxnet showed up that many control system users seemed to grasp the potential risks the systems might pose, given that many control systems weren't designed to resist Internet-borne threats, or perhaps ever see patches, although many run on Windows.

Ralph Langner--the German computer security expert credited with discovering Stuxnet-- has warned that "one can use exploit code to attack PLCs without any insider knowledge at all." Unlike a highly targeted attack such as Stuxnet, which was designed to only sabotage high-frequency convertor drives used in a specified uranium enrichment facility in Iran, Langner said that script kiddies could easily create PLC attacks without understanding the target environment.

Likewise, the prison control system and PLC research team reported that all three of its members quickly learned to "put together a PLC exploit in only a few hours," according to their research paper, owing to the simplicity of the programming languages involved. But an attacker might not even have to bother with that. "There are many exploits that are publicly available and can be found online such as on exploit-db.com," they said.

Given the potential threat posed by a cyber attack against the control systems or PLCs employed in prisons, what should be done? In particular, the research team suggests eight improvements, including restricting the use of physical media (which could carry malware) in facilities, segmenting networks properly, improving patch practices, as well as using heightened security procedures in all areas that rely on PLCs. Also reevaluate current prison designs. "Many modern prisons/jails were designed 10 years ago, before these attack vectors were known," they said.

On his blog, Strauchs said that whenever possible, prison systems also shouldn't be Internet-connected. "The correctional facility security system should not have external connections, or if that can't be avoided, connections need to be safeguarded by security protocols--not security-through-obscurity--and systemic technical countermeasures," he said. In addition, "no one should ever be permitted to use workstations for personal activities like checking private email or viewing images--both of which our team saw during onsite evaluations of correctional facilities."

Thankfully, said Strauchs, fixes appear to be underway. "We believe that the manufacturers are working on what they can fix and, as a result, we are not advocating removing PLCs from facilities but, instead, addressing the vulnerabilities through awareness and education of the people working in facilities with PLCs," he said.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

CVE-2014-7142
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (crash) via a crafted (1) ICMP or (2) ICMP6 packet size.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?