Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

9/23/2010
10:07 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Stuxnet Heralds New Generation of Targeted Attacks

Power plants no longer considered immune to infection, and targeted attacks become more precise

This is first in a two-part series on Stuxnet

It's the first known malware attack to target power plant and factory floor systems, but the Stuxnet worm also has opened the door to a whole new level of attack that could execute the unthinkable, manipulating and sabotaging power plants and other critical infrastructure systems.

Stuxnet has been under the microscope over the past few days as researchers around the world have picked apart and analyzed the malware's makeup and possible intent. No one knows for sure yet who is behind it -- many point to some nation-state link due to its many layers of expertise and the sophistication of the attack -- nor its specific goal, but most agree that it's a game-changer.

"We've never seen anything like this before," says Liam O Murchu, manager of operations for Symantec Security Response, which has been one of the leading teams of researchers to study the malware. "It infects those PLCs that control real, live machinery, and can have physical affects in the real world. Turning off essential parts of a plant could have drastic affects."

That could mean building up pressure in a plant system, reporting faulty data to a plant operator, or causing a complete failure of the power plant system, or some sort of catastrophe, says Eric Knapp, director of critical infrastructure markets for NitroSecurity. "People were focused on the Windows zero-days [in Stuxnet], but they were just delivery mechanisms. The concern is the payload: installing a rootkit on the control system and injecting code into PLCs. These are things that cause things to happen in the control system: so there's a potential for some pretty severe damage," he says.

Stuxnet has rocked the mostly insulated SCADA and process control world, which long had been considered relatively buffered from attack because these systems aren't Internet-connected. But with Windows systems supporting many of these plants, and the Stuxnet worm spreading via a USB stick, that was all it took to burst that bubble. "Eight months ago, there was no such thing as a virus in PLC. People thought you couldn't get to them," Knapp says. "This is proof that you indeed can infect a PLC. PLC is now an attack vector."

The Stuxnet worm first came to light over the summer and initially was considered yet another zero-day attack on Windows, exploiting the so-called "LNK" vulnerability in Windows machines via USB devices and fileshares. But upon closer inspection over the past month, it became clear that aside from its target of SCADA systems, this was no ordinary Windows attack. It exploits four different Windows zero-day vulnerabilities, including a print spooler bug and two others that escalate user privileges to first infect a Windows machine running Siemens software to manage control systems. It then looks for a Siemens S7 PLC, which it attacks and changes its programming by injecting code into it.

Symantec's Murchu says the worm has one rootkit that hides files on a UB key on the Windows machine to avoid discovery, and another rootkit that hides the code it sends to the PLCs. "It doesn't want the PLC to see those changes, because then it would realize something was wrong," Murchu says.

Stuxnet injects a piece of code into a Siemens control system -- past the SCADA and engineering software, and into the "ladder logic," says Gary McGraw, CTO at Cigital. "It's not just malicious code rooting SCADA boxes," he says. "It's after the control system and tries to inject some code into the logic controls of a physical process."

The worry now is that Stuxnet will be reinvented or reused in some form for other attacks. The concern is that future such attacks will be less likely to be discovered. "This malware takes some serious resources to get it accomplished, including covert operations and intell. But the real problem now that it's been discovered and researchers are taking it apart, the techniques it uses are available for everyone," McGraw says.

Stuxnet has even put the much-publicized and analyzed Aurora targeted attacks into perspective: the attacks on Google, Adobe, Intel and other major companies exposed earlier this year were spread via a relatively unsophisticated attack that went after an old browser, Internet Explorer 6. Although they indeed were successful in stealing some intellectual property, the attacks were nowhere near as complex as Stuxnet, experts say.

In an odd twist for an attack so laser-focused, the Stuxnet worm spread wide beyond its intended mark and into the wild, infecting Windows machines worldwide, nearly 60 percent of which were in Iran, according to Symantec's data.

Next Page: Attackers likely didn't intend for Stuxnet to spread Kelly Jackson Higgins is the Executive Editor of Dark Reading. 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

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27621
PUBLISHED: 2020-10-22
The FileImporter extension in MediaWiki through 1.35.0 was not properly attributing various user actions to a specific user's IP address. Instead, for various actions, it would report the IP address of an internal Wikimedia Foundation server by omitting X-Forwarded-For data. This resulted in an inab...
CVE-2020-27620
PUBLISHED: 2020-10-22
The Cosmos Skin for MediaWiki through 1.35.0 has stored XSS because MediaWiki messages were not being properly escaped. This is related to wfMessage and Html::rawElement, as demonstrated by CosmosSocialProfile::getUserGroups.
CVE-2020-27619
PUBLISHED: 2020-10-22
In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.
CVE-2020-17454
PUBLISHED: 2020-10-21
WSO2 API Manager 3.1.0 and earlier has reflected XSS on the "publisher" component's admin interface. More precisely, it is possible to inject an XSS payload into the owner POST parameter, which does not filter user inputs. By putting an XSS payload in place of a valid Owner Name, a modal b...
CVE-2020-24421
PUBLISHED: 2020-10-21
Adobe InDesign version 15.1.2 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious .indd file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.