mailing list archives
Re: Microsoft Office Excel 2010 memory corruption
From: Jeffrey Walton <noloader () gmail com>
Date: Mon, 29 Oct 2012 13:59:12 -0400
On Mon, Oct 29, 2012 at 1:35 PM, Peter Ferrie <peter.ferrie () gmail com> wrote:
How can i make sure a crash is not exploitable? (( The short answer is
simple assume every crash is exploitable and just fix it.))
No, it costs a lot of time and money to fix even one issue.
We don't want to waste it on something that isn't exploitable.
There are at least four problems with this argument. First, the
argument basically says "defective software is OK." I find that to be
negligent (perhaps grossly negligent), and it sets off red flags for
Second, if a shop did not get the basic coding correct, what
credibility does the shop have when they claim its not security
related and cannot be exploited. Often, the folks claiming something
defective is OK are either too dumb or too ignorant to realize they
are wrong. We saw the same with attacks on MD5 from the a number of
folks, including the CAs.
Third, its often easier to fix problems like this than spend the
man-hours studying it. Architectural defects are a different story
Fourth, the software does not meet basic merchanibility standards.
Would you accept an auto defect where your windshield wipers did not
work on occasion?
If a shop gets it wrong too often, I ban the company's software. For
example, I no longer suffer Adobe's bugs on my network because its not
worth my time to shut down the vectors.
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
Re: Microsoft Office Excel 2010 memory corruption Yuhong Bao (Oct 29)
Re: Microsoft Office Excel 2010 memory corruption kaveh ghaemmaghami (Oct 29)