Risk
1/16/2011
07:48 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Report: Stuxnet Joint Israeli-U.S. Operation

A story published this weekend adds evidence to what many have suspected all along: that the Stuxnet worm was nation-state designed and developed to set-back Iran's nuclear ambitions.

A story published this weekend adds evidence to what many have suspected all along: that the Stuxnet worm was nation-state designed and developed to set-back Iran's nuclear ambitions.According to unnamed sources in a story published in the New York Times Saturday, the Stuxnet worm was a two year long operation coordinated among the United States and Israel.

The Stuxnet worm was discovered this summer, and is the first publicly known worm that can snoop and re-program industrial control systems. And is widely believed to target Iranian nuclear centrifuges thought by many countries to be part of a weapons program.

According to the story, Stuxnet was thoroughly tested at the guarded Dimona complex in the Negev desert. It was at that site where Israel tested Stuxnet against equipment built to closely match what Iran was running at its controversial Natanz installation.

The paper also said that the U.S. Idaho National Laboratory identified vulnerabilities in the Seimens systems in use by Iran.

The worm, also in the report, is credited with not only with the ability to disrupt Iran's nuclear centrifuges but to only (incredibly) feed fake data back to technicians that made it appear all was well with the equipment:

The worm itself now appears to have included two major components. One was designed to send Iran's nuclear centrifuges spinning wildly out of control. Another seems right out of the movies: The computer program also secretly recorded what normal operations at the nuclear plant looked like, then played those readings back to plant operators, like a pre-recorded security tape in a bank heist, so that it would appear that everything was operating normally while the centrifuges were actually tearing themselves apart.

The worm is credited with sending back the alleged Iranian nuclear weapons program by several years.

It's impossible to tell if these reports are accurate. But I do believe we'll soon know who the creators of the Stuxnet worm are exactly.

No matter who created this worm, it's certainly changed the way we have to think about defending industrial control systems and our own critical infrastructure. That's because if Iranian systems are vulnerable to such attacks – so are ours.

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.