Oracle 'Worm' Exploit Modified
answers writes "Two months after an anonymous researcher released the first public example of an Oracle database worm, the exploit code has been advanced and republished, adding new techniques to attack databases. From the article: "It's still very theoretical right now, but I don't think any DBA should be underestimating the risk," said Alexander Kornbrust, CEO of Red-Database-Security GmbH. "If you're running a large company with hundreds of valuable databases, a worm can be very destructive. It is very possible to use this code to release a worm. I can do this right now if I wanted to.""
It is very possible to use this code to release a worm. I can do this right now if I wanted to.""
That seems like an odd quote. Did the author of the article like Double-Dog dare him, or something?
The theory of relativity doesn't work right in Arkansas.
It is very possible to use this code to release a worm. I can do this right now if I wanted to.
MICHAEL
I'm gonna find out the hard way that I'm not a pussy if they don't start treating us software people better.
SAMIR
That's right.
MICHAEL
They don't understand. I could come up with a program that could rip that place off big time...big time.
PETER
Yeah.
As a consultant, I once nearly destroyed 2 years worth of a companies research data my first week on the job.
I ran some perl script that they had written against a test database to update some stuff. Unfortunately, it turns out that the real database address was hardcoded deep in the Perl, and I hadn't understood this. The DB admin complained after it had run about 5 minutes updating (incorrectly) their multi-gigabyte database that access to the database was slow. So I immediately hit ^C and said, "OK, let's get the backup tapes!" I had actually asked previously whether there were backups, so I was pretty confident I was going to get out of this one. The response elicted sheer terror: "Oh, we don't back up the database!" Transaction logging wasn't turned on, either. They thought they might have a 6-month-old CD burn of the data somewhere, but they couldn't really find it IIRC.
Fortunately, the script had been written to do its transaction atomically, so the database changes got rolled back before any damage was done. You can guess what my first project was after changing my pants.
Some of my friends have stories in this vein also. Companies are less careful with their databases than you would think.