Forum Moderators: open
[secunia.com...]
The vulnerability is caused due to insufficient validation of drag and drop events issued from the "Internet" zone to local resources. This can be exploited by a malicious website to e.g. plant an arbitrary executable file in a user's startup folder, which will get executed the next time Windows starts up.
Microsoft officially will only release patches every 2nd Tuesday of the month. That's almost a full 30 days away. Save yourself some pain, switch to FireFox, Opera, etc.
Then again I don't use IE... ;)
How to crash Internet Explorer (and therefore Windows) in 11 bytes!
Step 1:
Create a file with just the following markup, and save it as
test.html (or whatever): [b]<style>@;/*[/b] Step 2:
Open the file in IE. Kaboom! That's all, folks. I think it still works in SP2, but I'm not sure.
After wasting few hours I moved to Firefox both at home and at work and feel no regrets.
Funny. It doesn't even say goodbye when it does that. Just *poof* and gone. Well, actually, not even *poof*. Just gone.
Why?
If the question was why does that code crash IE, then a pretty good explanation is here - [seclists.org...]
1) XP users can "rollback" their system to pre-IE-update condition and start over
2) In Add/Remove Programs, when you select IE to uninstall, it offers to "rollback" to the previous version, if you have kept the files required to do so...which you should always do for at least one generation of MS releases...just in case.
I know on several systems, installing the IE6 "upgrade" and then returning to windowsupdate produces lots of errors with the MS site. To fix it, you've got to do the "rollback" thing, install the rest of the security updates, set your security to low-medium, and THEN try the "upgrade". That usually works, for those who can't do without IE.
Very happy with Firefox, thenk ewe. I'll take modularity over integration in any situation where it is not absolutely necessary...and this is clearly one of those instances.