Microsoft’s Real Test with Vista is Vulnerabilities
vista, the solution to all our problems: microsoft portrays vista as anything from the end of software vulnerabilities to the end of spyware.
in my opinion, that is irrelevant as both problems are not going to go away. they are part of how software systems and the internet work, and that’s that. the bad guys with their roi won’t give up that easily.
what is going to happen though is that creating and exploiting these would become more difficult.
vista is not the holy grail or some “silver bullet”. it is a test for microsoft. it will be a clear indication of how far microsoft has advanced in the realm of developing secure software, if at all.
in the past i posted claims that stated microsoft has advanced considerably in recent years, and today, it has become very difficult to find vulnerabilities in microsoft products. naturally this doesn’t apply to internet explorer.
their code is very professional and heavily reviewed. unless you spend significant resources and time on the task, you are not likely to find even denial of service vulnerabilities, not to mention code execution vulnerabilities in their code.
when you do find one, the vulnerability will most likely be a logical flaw. microsoft has no problem committing incredible resources to code review.
however, we need to take into account the excel case:
last december noam wrote of ebay bids on an excel 0day vulnerability, which later on were also announced on the full-disclosure mailing list.
the issue of bidding for exploits on ebay lead to a heated discussion and many blog entries.
in the coming months after that, microsoft announced in it’s monthly security patches release (patch tuesday a.k.a. black tuesday) several excel vulnerabilities.
in this last month, it happened again.
then the first (but not last!) of the excel 0days was disclosed. here is what juha had to say about it.
what does this mean, and how does this work with what every decent reverse engineer will tell you: microsoft’s code is very professional.
the answer is divided into two:
2. untouched code-base.
microsoft is basically using legacy code that has been reviewed and attacked countless times by countless people since windows nt if not, in some cases windows 3.1 (gdi32.dll anyone?).
is it any wonder new vulnerabilities are so difficult to come by? everyone in the industry has been trying for, at the very least, over a decade. we can’t tell if their code is that good due to their ability.
excel on the other hand is code-base which didn’t in the past receive that same kind of scrutiny very often. when the kiddie on full-disclosure and ebay issued his challenge, what happened was that many people started aiming at excel.
several patch releases with official bullet-ins, several 0days… fun, ain’t it? not related you say? maybe.
so.. yes. microsoft’s code is very professional, but we can’t really rank their ability on it due to the immense efforts by everyone outside of microsoft to do their qa for them.
when vista comes out, regardless of all the cute security features it will have. some of which will raise the bar for security researchers, it will have vulnerabilities.. and not too long after the release.
the amount of vulnerabilities and their complexity will tell us more of microsoft’s real ability with security today, than anything else.
microsoft can claim vista is the holy grail all they like, and indeed, some of these security features are intriguing… in my opinion though, the real question is what vista will show us:
1. it’s a new untested code-base out for play.
2. microsoft supposedly learned a thing or two since windows 95.
your guess is as good as mine and the results of this test will be very telling.