Myrddin Emrys
No favorite files added yet
(Mar 30, 2007 - 1:32 PM)
I'm sorry, but this is not exactly true. There are two major classes of exploit: Programs that can attack the system, and Data that can attack a program.
It's almost impossible to protect against a malicious program. Viruses and Spyware run rampant, and if a user allows them to run it's difficult if not impossible to prevent them from harming the computer.
But it is relatively easy to prevent malicious data to attack the system. Malicious data should be preventable... programs should check the data before running it, should confirm that the input data is valid. Insecure programmers and permissive programming languages are what allow bad data to harm the system.
So the point is that a Microsoft system driver, a driver that is critical to the second-to-second operation of the computer, a system driver that needs to function even when everything else is crashing... is NOT checking its input data.
That is worse than having a third-party driver, written by some random mouse manufacturing company, being poorly written. This is a Microsoft driver, written by a company that should know what portions need to be most secure, screwing up and RE-INTRODUCING a bug they already fixed years before.
Inexcusable.