navti said:
it all happened automatically without any intervention. i was using
win2k and ie6 at the time. i have since switched to mac os x. ...
if ((JVM_vers[0]!=0)&&(JVM_vers[2]<3810))
{ ExploitNumber=1; }
else // if JVM = 5.0.3810.0 or higher
The (dreaded) MSVM.
If this script found a 3809 or previous build MSVM, it
might have taken advantage (using a Java applet) of any
number of security holes in those Microsoft VM's.[snip]
he stole my files . i know this for a fact.
why would you think it was otherwise ? have you been living down a
mineshaft for the past 5 years ? never heard of xss ? are you in some
sort of state of denial ?
only an ignoramus would try and deny it was possible for a webserver
to compromise a client's machine.
my mistake is thinking javascript was enough . obviously it was a
combination of javascript, java, activex , php , xml etc etc
It looks to me - and I could be wrong - that it pushes a buffer overflow
to the browser to start existing code. I'd have to pull it to bits to be
sure what its doing, but it seems it is using Javascript to build a page
existing code can read so that it knows what exploit to run.
If that's right - and as I say, it may not be - then it means that you
would have earlier agreed to let that code onto your machine either
explicitly or by having very low security settings on your browser. Low
enough that it can pretty much only be IE. It then exploits existing
software on your machine, such as Norton, McAfee and the old MS JVM
apparently.
Though I agree with the others so far, unlike them, I do think that once
it has got that far, it is quite possible to steal your files. I'd need
to see the code it on your system, but this kind of apparent "drive by"
as you call it is not really what you think. Its a double-attack; you
get apparently "safe" code on your system, later on you start it from a
site that doesn't carry any invasive code - in this case, a bit of
Javascript.
At that point, the code sitting quietly on your machine leaps into
action, does its thing and shuts up. Its a trojan, pure and simple. The
Javascript just exploits IE to start the trojan and it is the trojan,
not the Javascript, that does the damage. WIth luck, the person that
gets hit is daft enough to think its that one website that causes the
problem, so doesn't realise the *real* problem is still sat on his
computer - the trojan.