Risk
1/16/2011
07:48 PM
George V. Hulme
George V. Hulme
Commentary
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
Latest Comment: nice one
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-1235
Published: 2015-04-19
The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in the HTML parser in Blink, as used in Google Chrome before 42.0.2311.90, allows remote attackers to bypass the Same Origin Policy via a crafted HTML document with an IFRAME element.

CVE-2015-1236
Published: 2015-04-19
The MediaElementAudioSourceNode::process function in modules/webaudio/MediaElementAudioSourceNode.cpp in the Web Audio API implementation in Blink, as used in Google Chrome before 42.0.2311.90, allows remote attackers to bypass the Same Origin Policy and obtain sensitive audio sample values via a cr...

CVE-2015-1237
Published: 2015-04-19
Use-after-free vulnerability in the RenderFrameImpl::OnMessageReceived function in content/renderer/render_frame_impl.cc in Google Chrome before 42.0.2311.90 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger renderer IPC messages ...

CVE-2015-1238
Published: 2015-04-19
Skia, as used in Google Chrome before 42.0.2311.90, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via unknown vectors.

CVE-2015-1240
Published: 2015-04-19
gpu/blink/webgraphicscontext3d_impl.cc in the WebGL implementation in Google Chrome before 42.0.2311.90 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted WebGL program that triggers a state inconsistency.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.