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

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: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6213
Published: 2014-04-19
Unspecified vulnerability in Virtual User Generator in HP LoadRunner before 11.52 Patch 1 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1833.

CVE-2013-6214
Published: 2014-04-19
Unspecified vulnerability in the Integration Service in HP Universal Configuration Management Database 9.05, 10.01, and 10.10 allows remote authenticated users to obtain sensitive information via unknown vectors, aka ZDI-CAN-2042.

CVE-2012-0871
Published: 2014-04-18
The session_link_x11_socket function in login/logind-session.c in systemd-logind in systemd, possibly 37 and earlier, allows local users to create or overwrite arbitrary files via a symlink attack on the X11 user directory in /run/user/.

CVE-2012-6646
Published: 2014-04-18
F-Secure Anti-Virus, Safe Anywhere, and PSB Workstation Security before 11500 for Mac OS X allows local users to disable the Mac OS X firewall via unspecified vectors.

CVE-2013-4279
Published: 2014-04-18
imapsync 1.564 and earlier performs a release check by default, which sends sensitive information (imapsync, operating system, and Perl version) to the developer's site.

Best of the Web