, SecurityFocus 2003-08-19
The Slammer worm penetrated a private computer network at Ohio's Davis-Besse nuclear power plant in January and disabled a safety monitoring system for nearly five hours, despite a belief by plant personnel that the network was protected by a firewall, SecurityFocus has learned.
Expand all |
Post comment
Slammer worm crashed Ohio nuke plant network
2003-08-20
JeiAr (1 replies)
JeiAr (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Dmitriy <maniac (at) angrycube (dot) com [email concealed]> (4 replies)
Dmitriy <maniac (at) angrycube (dot) com [email concealed]> (4 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-21
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Anonymous (1 replies)
Anonymous (1 replies)
Unbelieveably Irresponsible
2003-08-21
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2007-05-19
mg (at) alienmicro (dot) com [email concealed]
mg (at) alienmicro (dot) com [email concealed]

Lets also talk about patching after the initial installation of an OS. I can recall doing this on Redhat and Solaris both. I guess that's a band-aid scenario there, as well? Howcome nobody mentions that in these articles? How convenient.
Instabilities in Windows? I have Windows Servers that have better uptimes than nix boxes running production. I'd be willing to guess that most of you saying Windows 2000/2003 is unstable haven't really used the product. Because you've sat at the console, done an installation and installed a few next-next-next programs doesn't make you an expert.
The fact of the matter is, any monkey with half a brain can install an OS and get it working. This is even the case with Solaris and Redhat (While I will say RH is much easier to install).
It takes a whole different kind of monkey to prep the server for production, fine tune and implement effective security policies. I don't mean just with the software. Educating your users and bringing them to understand the dangers of irresponsible computer use is an important step in ensuring the integrity of your network. The fact of the matter in this story is the network was improperly secured, and probably due to a lack of documentation and communication between the staff members responsible.
The same thing could have happened on a nix infrastructure left vulnerable to attacks. Lazy sysadmin'ing and not applying patches doesn't just affect Windows. It affects EVERY OS out there.
So stop using Microsoft as a scapegoat and start doing your job properly!
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/6767/21759#21759