Word 2007 crashes: A feature, not a bug?
- IT TOPICS:Desktop Applications, Security
Let me see if I understand Microsoft's philosophy about malformed documents that crash Word 2007. In the words of an unnamed Microsoft spokesmushroom: "In fact, the behavior observed in Microsoft Word 2007 in this instance is a by-design behavior that improves security and stability by exiting Microsoft Word when it has run out of options to try and reliably display a malformed Word document....The sample code in [Aharoni's] postings cause Microsoft Word to crash, and users can restart the application to resume normal operations."
So can we expect to see that approach in other products that use Windows Embedded?
Like maybe...a TV that, when the cable service goes pixellated, shorts out all the circuitry in your house? ("Users can reset circuit breakers to resume normal operations.")
A car CD player that, when it's fed a scratched disc, disconnects the steering and brakes and disengages the clutch? ("Users who survive can restart the car to resume normal operations.")
A cell phone that, when the conversation gets too banal, shuts down your relationship? Oh, wait -- that's been done.
David LeBlanc -- quoted in the news story as a Microsoft secure-code guru -- says "it is better to crash, at least with client apps, than it is to be running the bad guy's shell code." Hooey. This is no either/or situation. For years, Word has been able to announce that a document is malformed and can't be loaded. (Which Word regularly does to me with file formats it doesn't recognize, so I know that notion isn't new to Microsoft's programmers.)
If your application code is in control, it can gracefully reject bad input.
If your app code ISN'T in control, you crash. You're already owned.
This suicide-before-capture approach isn't "by-design" behavior. It's lack-of-design behavior.
And a "code guru" of any kind who thinks that's not a security and stability problem that needs fixing doesn't belong in this business.



