Oracle 'Worm' Exploit Modified 87
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.""
yeah. (Score:4, Funny)
That seems like an odd quote. Did the author of the article like Double-Dog dare him, or something?
Re:yeah. (Score:1)
Re:yeah. (Score:3, Funny)
You posted this on a Saturday at 4:46PM - sorry, 'fraid not, the banks are all closed...
Re:yeah. (Score:1)
Re:yeah. (Score:5, Funny)
Re:yeah. (Score:1)
Perhaps a slight breach of etiquette occurred by skipping the triple dare and going right for the coup de grace of all dares, the sinister triple-dog-dare. But I can't be certain.
Re:yeah. (Score:1)
firewalls? (Score:5, Insightful)
Of course this is an exploit but the impact shouldn't be overrated.
Re:firewalls? (Score:1)
The Realm of the Professional Cracker (Score:5, Insightful)
How many oracle db's are connected directly to the internet? Even within most company's their isnt a direct connection option to the db but only thru an application.
Here you begin to enter the realm of the professional cracker [apologies to chef [southparkstudios.com]], my little padawan novitiate.
The professional employs something like the WMF vulnerability to crack the client OS, and then uses the client application to crack the DB.
And when he's seen what he needs to see, the professional tidies up and removes any evidence of his intrusion.
In all seriousness, the PRC Red Army's "TITAN RAIN" operation is more than a little troubling in this regard:
Re:The Realm of the Professional Cracker (Score:1)
I still need to see the first worm who uses such techniques.
Re:firewalls? (Score:1)
*head explodes*
Re:firewalls? (Score:2)
Of course this is an exploit but the impact shouldn't be overrated.
First, it's not an exploit but merely a try-8-default-accounts code. Poor coding style too, I have to say...but someone seems very proud of it???
What's really interesting about this worm is that it's written in PL/SQL, i.e. it runs on an ORACLE server itself. If it was really cle
Re:firewalls? (Score:3, Insightful)
Shouldn't that be "how many oracle db's are connected directly to computers which might get infected with a virus"?
e.g. plenty of firewalled LANs got CodeRed, Sasser, etc. (including that nuclear power station which nobody thought was internet-connected)
Re:firewalls? (Score:2)
It wasn't internet-connected. Some IT dude brought the virus in on his laptop. (Not that this doesn't make the incident less dangerous. A determined attacker could infect an employee at home, and then undermine the security of the corporate network / nuclear power plant as an insider. Difficult, but scary!)
Re:firewalls? (Score:1)
I suspect we may be arguing similar things here, but:
"Internet connected" in the virus-containment sense, means things which process data which originated on the internet. Whether that happens via a router, or ethernet cable, or firewall, or laptop, or USB key, or someone typing it in, is somewhat irrelevant, so long as data can travel from one to the other.
Maybe "indirectly internet-connected" would be a better
Re:firewalls? (Score:2)
Sasser (the MS-SQL worm) also targetted a lot of desktop configurations, due to the fact that certain versions of MS-Office come MSDE, a cut-down MSSQL. I don't know how many people run "deskop Oracle", but I suspect it's pretty tiny compared to MSDE.
Also, unlike MS-SQL, Oracle is pretty much non-existant in the small business space where networks and patching are haphazard. Your typical Enterprise Oracle install is firewalled up the wazoo.
Re: (Score:2)
Re:firewalls? (Score:1)
Heh, that's two more characters than a lot of MSSQL passwords I've seen.
Backup Data? (Score:5, Insightful)
Re:Backup Data? (Score:2)
Oracle databases can get rather large, and are used in real-time transactional environments. Do you have an idea how long it would take to restore, say, 900GB of data from backups, and how much money would be lost while the Oracle database would not be able to process transactions for the company?
Re:Backup Data? (Score:1)
Just a rough estimate.
Re:Backup Data? (Score:2)
2-4 hours for a restore of a 900 gigabyte database? From my experience I'd say that sounds overly optimistic, but of course the time taken to restore is highly dependent upon your database architecture, infrastructure and backup plan.
Is that from tape? optical media? cartridge? Disk? Is that a hot or a cold backup? Is it rman, or some other backup tool, or just a copy of the underlying file systems?
Re:Backup Data? (Score:1)
Re:Backup Data? (Score:2)
As the database runs, you write a copy of the transaction log to a DVD-R (or o
Re:Backup Data? (Score:1)
I think you underestimate the restore time. I've been involved in some Oracle restore tests recently, and there are some twists you're not considering. First, what's the backup strategy? Many databases are not backed up 100% every day; more typical is a full backup every 14 days with incremental backups in betwee
Re:Backup Data? (Score:2)
Second of all, the fact that you're thinking in terms of "oh, it's only a few hours" suggests to me that you've never worked for a company where every minute costs an incredible amount of money. Multiply each hour you need with a few million dollars, and you'll be starting to see why this can be a big deal.
Re:Backup Data? (Score:5, Insightful)
If I combine everyone from my company and all companies we cooperate with, I can name only two people who consider backups to be anything but an annoying waste of time some pessimists are blabbing about in order to suck in some of their money.
Redundant hardware runs against the principle of cutting costs; no bean counter would even consider investing in data integrity.
When I tell people that I installed a script that will back up the most valuable part of the data and dump them to a remote location, the reaction is like: uh, cool, but what if it breaks things?
Re:Backup Data? (Score:2)
> These will either get fired, killed or their companies will fail. Either way, they do not need to be worried
> because they are hopeless.
That *might* make sense if only 1-5% of the dbas out their were incompetent. Unfortunately, that number is probably more like 50-60%. And those databases that do fortunately have a competent dba often don't have competent management - that would pay to test
Re:Backup Data? (Score:1)
Typically if a company has shelled out the cash for Oracle, they'll also have a handful of competent DBAs on staff. Were this Access or MSSQL it would be one thing - I've known plenty of terrible DBAs, but they typically weren't on the Oracle side of the curve.
That being said, I am in complete agreement (and fear) about the competence of most administrators out there.
Re:Backup Data? (Score:2, Funny)
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,
Re:Backup Data? (Score:3, Interesting)
Re:Backup Data? (Score:3, Interesting)
I changed that one quoted term to make a point: if we aren't going to be concerned here, why be concerned about all those other worms. Oh, I know... perhaps because having your servers in an unusable state while performing recovery is a bad thing which can cause serious financial and reputation
Re:Backup Data? (Score:2)
Unless the worm modified some data which got backed-up. A week later, the untainted backups would be history.
(And even if you kept monthly backups, who's going to try restoring them without losing a month's work for the whole company?)
doesn't exploit a vulnerability (Score:5, Informative)
Given enough databases, someone will forget to change these. For that reason any shop with more than a half-dozen databases should be using some kind of application policy-checker that will automatically test for this kind of a policy violation.
Re:doesn't exploit a vulnerability (Score:3, Informative)
Nope, scott/tiger is deprecated -- the current sample schemas are separated into multiple users, and they are all disabled by default. These users are installed by default, but it's not hard to tell Oracle to not install them.
Of course, there's a lot of non-10g databases out there. Heck, there's a lot of pre-8i databases out there still even though you have to pay an arm, leg, and torso for support, if y
Re:doesn't exploit a vulnerability (Score:2)
Re:doesn't exploit a vulnerability (Score:1, Insightful)
Since when does a windows vulnerability (or other network security failure) qualify as a weekness in Oracle?
If the System administrators don't do their job, you don't have a system anyway.
Re:doesn't exploit a vulnerability (Score:1)
"[i]"It's still very theoretical right now"[/i]
I'm sorry for possibly flaming now, but this is FUD from GmbH firm to a US firm. Informational yes, serious not really (for enterprises that is).
Re:doesn't exploit a vulnerability (Score:1)
> with [i]your[/i] schema setup/install scripts. It would be second nature to secure the DB at the
> install (as taught in many Oracle adv. DBA classes).
Sure, but many databases are installed by extremely junior personnel. Sometimes somewhat-embedded within an application, at other times stand-alone.
I've found as a sr. dba that setting up a dozen secure databases to be a challenge without tools t
Re:doesn't exploit a vulnerability (Score:2)
I remember a recent M$ security releated article - it came with a M$ security add running beside it "we don't give Trojan horses a change". Bwahahaha ROFLOL.
Article summary (Score:1, Redundant)
Human's Love To Catagorize (Score:2, Interesting)
Re:Human's Love To Catagorize (Score:1)
Do you really think there aren't organizations out there with similar resources to this company whose aims are finding vulnerabilities like these for the purposes of exploiting them?
If he can find it, someone else can. Informing the public that an exploit exists increases pressure on
Blackmailing Oracle (Score:3, Interesting)
Doesn't this sound very much like something a blackmailer would say?
Alexander is an ex-Oracle employee. I wonder if he was let go because of his poor judgement.
Re:Blackmailing Oracle (Score:1)
Apparently we are dealing with Milton from Office Space: http://www.lostandfrowned.com/miltoncd.gif [lostandfrowned.com]
Re:Blackmailing Oracle (Score:1)
obZealotry (Score:1, Redundant)
Re:obZealotry (Score:1)
Re:obZealotry -- What? (Score:2)
This sounds so familiar. (Score:3, Funny)
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.
Re:Really, really, really lame (Score:1)
Professional? We are in the middle of a $5 million Oracle Financials implementation. I have never met so many inept consultants in my life. Granted, IT consultants in general are oversold, but these guys and girls take the cake. I had a "Senior DBA" that required three conversations to be able to change her password at the CLI. When I bitched to the Oracle project manager about it (imagine this type of thing about 8 times a day), he said Oracle doesn't expect it's sen
Re:Really, really, really lame (Score:1)
Security (Score:1)
Re:Security (Score:1)
Sure, but look at all the non-skilled labor now doing this work. Whether due to outsourcing, attempts to save labor money, etc - I see a ton of very junior people doing installs. The major databases now have install wizards that are pretty good - and allow complete amateurs to install the product. This is great. But these folks have no idea how to lock down the database once they've installed it.
And think beyond oracle to mysql - where almost no dbas install
Re:Security (Score:1)
My 2 Cents (Score:1, Insightful)
Regardless of the exploit taken, if the DB is properly configured and secured the only "lost" of data should be against the schema being attacked. And then you can use Oracle's Flashback [oracle.com] technology to roll back that one transaction - if caught in time.
True loss of data means the DBA did not do their job. Of course, this is usually, in my experience anyway, the fault of managment and the business - budget/time/resources.
logon trigger aa blocked by Google? (Score:1)