@Can you really be so ignorant
I'm not ignorant. I'm actually pretty good, and I wouldn't be at all surprised if I found that you use some of my code on a daily basis - and I bet it doesn't go wrong for you! :-)
As for "...which has features you can code or configure into the application..."
...that completely misses the point, and you are making excuses for a fundamentally broken model. The point I was making (and despite what you infer, this IS mostly a MS-only problem) is that stuff like this should not be possible. The reason is IS possible is because (a) the OS mechanisms that get exploited are not robust enough and (b) bits of application are getting more and more ingrained into the OS in a way that makes exploits like privilege promotion possible. The division between OS and application is blurred to the point where there are numerous back doors and hooks into the OS that should never have existed in the first place.
Bugs in software is a fact of life and if you have an exploitable bug then you have to expect bad things to happen. But "bad things" should be confined to data in use (or at most, the user's account). "Bad things" should not extend to the point where rogue code can execute random routines that can cause damage to the OS or give root privileges to some remote bot somewhere (I know this is problem is not cited in this case, but it HAS happened many times in the past). These things should not be possible. The fact that they are shows a fundamental failure in the OS model.