Attacks/Breaches
2/14/2011
01:23 PM
Connect Directly
RSS
E-Mail
50%
50%

Stuxnet Iran Attack Launched From 10 Machines

Symantec researchers analyzed the worm's timestamps and found that the 12,000 infections they studied originated from a handful of machines.

Top 10 Security Stories Of 2010
(click image for larger view)
Slideshow: Top 10 Security Stories Of 2010

All Stuxnet worm attacks -- which targeted a nuclear facility in Iran -- were launched by infecting a total of just 10 machines. In other words, the more than 100,000 Stuxnet infections spotted by September 2010 can be traced back to a handful of infections, which likely targeted peripheral facilities to ultimately infect the true target.

That's the surprise finding from a new Symantec report on Stuxnet, released Friday.

Stuxnet was designed to sabotage the high-frequency convertor drives used in a uranium enrichment facility in Iran. The malware adjusts the automated control system's user interface to make it appear that the drives are running normally. But in reality, the malware is quickly adjusting the speed of the drives to very high and low frequencies. As a result, not only does the uranium not get enriched, but the drive motors are permanently damaged.

In November, Symantec's researchers discovered that Stuxnet records a timestamp every time it infects a new machine. "However, at the time, this information was largely useless as we did not have enough samples to draw any meaningful conclusions," they said in a blog post.

Since then, however, numerous antivirus firms have been feeding the researchers every Stuxnet variant they capture, enabling them to amass a collection of 3,280 unique samples, which would have generated about 12,000 infections. Studying this subset, they found that every infection could be traced back to just one of 10 machines.

Since attackers may not have had direct access to the enrichment facility, it’s possible they targeted machines in five related facilities, in an attempt to spread the malware to the enrichment facility. Interestingly, in June 2009, and again in April 2010, the same PC appears to have been infected with different versions of Stuxnet. Meanwhile, another facility was targeted once, but had an initial three infections, which Symantec said suggests that a USB key carrying Stuxnet was inserted into three different PCs.

Symantec said the last Stuxnet attack appeared to have been launched in May 2010, while the earliest known attack dates from June 2009.

Iran began containing Stuxnet in August 2010. "Looking at newly infected IP addresses per day, on August 22 we observed that Iran was no longer reporting new infections," said Symantec's researchers. "This was most likely due to Iran blocking outward connections to the command and control servers, rather than a drop-off in infections."

But Iran's response came too late. According to news reports, the Stuxnet attacks appear to have been successful.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.