The executable file doing the damage is iexplore.exe or acrobat.exe. Not allowing an LUA to install it's own software is irrelevant, iexplore.exe IS allowed run, hence, the malware gets to do it's thing if it exploits a flaw in that exe.
How does this occur if neither acrobat.exe nor iexplore.exe is installed on my system?
No no no no no - you clearly have no idea what a buffer over flow bug is, or how it works.
A program like IE is running. It has a bunch of stuff in RAM, a mix of data and code, all of which is has permission to execute, because it put it there, and because it is a program that is allowed to run. With a buffer overflow you write data beyond the end of where it should have gone, and over into the bit of RAM owned by IE where IE is keeping it's executable code. IE then runs that code, assuming it is it's own code. The RAM belongs to IE, is edited by IE, and is executed by IE. It has all the permissions IE does.
In short - a LUA provides zero protection.
Again, as Internet explorer is not installed on my system, how do IE buffer overruns occur?
And if you are making such an issue of buffer overruns, I assume you have a buffer overrun memory firewall installed on your system? Why fool around with overruns when a free solution is available? I also assume you regularly test your system for buffer overrun vulnerabilty? Again using a free tester.
The blaster worm exploits a flaw in the RPC service which is on by default, and runs with system level privileges. It doesn't matter a JOT what user is logged into the system, or what level that user's account has, Blaster does not enter userspace, it works at the system service level. User accounts literally don't enter into it. Like I said - Blaster can infect a system WITH NO ONE LOGGED IN AT ALL.
I get the impression you do not understand how modern multi-user operating systems are architected at all. There simply is no link between low-level services and regular user accounts.
Again, the Remote Procedural Call you reference must occur through port 135. When you get infected the RPC will invoke a system shutdown. At this initial stage you can abort the shutdown and trivially remove Blaster.
Assuming a successful restart occurs and not a crash, an entry is made into the following Registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\windows auto update The string found at this entry is mblast.exe
Notice the registry key is Windows update. A limited user does not have the required permissions to run Windows Update.
I thought you didn't run any AV? So how exactly do you expect anti viral software to pick it up? If you are running all the software you list above then it's hardly realistic to say you don't run AV! Also - Window automatically runs a malware removal tool behind the scenes as part of Windows Update these days. So goodness knows what has been cleaned up after you that you're just not aware of.
I never said any such thing, you did. In your zeal to insult me and brag about your knowledge, you didn't take the time to read my post. I said during the past 11 years of visiting some of the most dangerous webs out there on a daily basis, I have yet to experience a single malware event. I said that was due to my using a Limited User account.
I said I run all sorts of anti malware software and they always return zero results. I also said every one of the computer noobs who I help, who I've set up in LUAs, have also had zero malware events since I set them up.
Also I never said I run Windows Update, you did. I have banned Active X controls from my system as they are extremely dangerous security risks. I obtain critical updates from 3rd party sources and install what I consider needed manually.
I have taken numerous steps to lock down my computer with settings, its easy to do, a LUA is the main one and just one of many.
That and you could be lucky. You have been doing the equivalent of sleeping around without protection. Not everyone who does that gets an STD, and not everyone who fails to run AV gets nobbled. Luck exists, it is real.
Then you must consider Unix users and Mac users internet whores as well since I am doing pretty much the same thing they do, that is not surfing as ROOT.