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.

Comments
Stuxnet 'Patient Zero' Attack Targets Revealed
Newest First  |  Oldest First  |  Threaded View
RetiredUser
RetiredUser,
User Rank: Ninja
11/13/2014 | 6:51:44 PM
Insider Espionage?
If we are to take the information at face value, we need to think about how worms like Stuxnet are implemented.  If the computer at Foolad Technic Engineering Company was infected just hours after the worm's creation, then yes, the idea of infection via USB isn't as likely, unless the worm was either written there onsite (which could have even been done on the first computer infected) or it was downloaded by an insider who was in communication with the Stuxnet authors and was waiting for it to be completed before downloading it.  There is great significance in the short time frame between creation of Stuxnet and infection of the first computer.  We could be looking at insider espionage, and investigation of who was working at Foolad during that timeframe will likely lead to identification of the original perpetrators.  I'm no political scientist, but after reading all the original articles linked from the Wikipedia page on Stuxnet, and newer ones since, one wonders if we aren't actually looking at self-sabotage (whether or not the actual writers of the code were based in Iran – it could have been made to order).  

I recall reading that several facts of the attack would make self-sabotage out of the question, the argument being that if the Iranians at the plants were going to sabotage themselves, they wouldn't create such a complex worm to do it.  Expense, intelligence involved, sheer hours to develop the work and the fact all the exploits it used were exposed and can't necessarily be used again; all point to external players.  Additionally, highly-guarded authentic private keys from two large companies were compromised and used to digitally-sign the worm, making the software "authentic", and the fact that four (at least) zero-day exploits were used to spread this worm - hardcore.  But I'd argue that we've seen more sophistication in the Middle East that we'd previously given credit for, even if it was gained through working with outsiders.  Remember, these plants are staffed with sharp engineers and whatever the reason for it, there could easily have been a motive for someone in one of the organizations listed, Foolad standing out, to kick off Stuxnet.         
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
11/12/2014 | 8:47:01 AM
Re: stuxnet
Yes, I definately want to put the book on my reading list...
Bprince
Bprince,
User Rank: Ninja
11/12/2014 | 8:17:01 AM
stuxnet
The malware was a game changer in so many ways. Looking forward to reading this when I get a chance.
RyanSepe
RyanSepe,
User Rank: Ninja
11/12/2014 | 7:46:39 AM
Re: Stuxnet
Agreed, it truly is fascinating and terrifying at the same time. Has this attack evolved since its original inception or has it remained pretty close to a constant?
Thomas Claburn
Thomas Claburn,
User Rank: Ninja
11/11/2014 | 5:25:18 PM
Stuxnet
I find the Stuxnet endlessly fascinating. I look forward to reading Kim Zetter's account.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-35942
PUBLISHED: 2022-08-12
Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. When the extended filter property `contains` is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data ...
CVE-2022-35949
PUBLISHED: 2022-08-12
undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `http://127.0.0.1` or `//127.0.0.1` ```js con...
CVE-2022-35953
PUBLISHED: 2022-08-12
BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Some links in BookWyrm may be vulnerable to tabnabbing, a form of phishing that gives attackers an opportunity to redirect a user to a malicious site. The issue was patche...
CVE-2022-35956
PUBLISHED: 2022-08-12
This Rails gem adds two methods to the ActiveRecord::Base class that allow you to update many records on a single database hit, using a case sql statement for it. Before version 0.1.3 `update_by_case` gem used custom sql strings, and it was not sanitized, making it vulnerable to sql injection. Upgra...
CVE-2022-35943
PUBLISHED: 2022-08-12
Shield is an authentication and authorization framework for CodeIgniter 4. This vulnerability may allow [SameSite Attackers](https://canitakeyoursubdomain.name/) to bypass the [CodeIgniter4 CSRF protection](https://codeigniter4.github.io/userguide/libraries/security.html) mechanism with CodeIgniter ...