Unique Major hashes are more likely to be unique bugs, while unique Minor hashes may be variations of the same bug. More specifically, the !exploitable extension produces a Major hash and a Minor hash.
Openoffice vs.microsoft office software#
However, there is not a one-to-one mapping of unique crash hashes to software bugs. Office XP has the most unique crashes of any of the Office suites. As indicated by the first five columns, there is a clear decrease in the number of unique crashes with the Microsoft Office products. This graph shows the results from all of the products.
Openoffice vs.microsoft office professional#
Microsoft Office 2010 Professional (released June 15, 2010)Īll Microsoft Office products were fully patched with updates as of November 2010.Microsoft Office 2010 Professional (File validation disabled).Microsoft Office 2007 Professional (released January 30, 2007).Microsoft Office 2003 Professional (released November 17, 2003).Microsoft Office XP Professional (released March 5, 2001).I tested currently supported Microsoft Office products: I used the same set of 190,000 mutated files to test each Office suite. Each seed file was mutated in 10,000 different ways, resulting in a 190,000-iteration fuzzing campaign for each target application. The range used for this test was to mutate 0.001% to 1% of the seed file for each iteration. The fuzzer used a random byte mutation strategy, which set the value of a range of bytes to a random value. I configured the fuzzing framework to use a set of 19 different DOC files. Note that !exploitable may assign different hashes to the same underlying software defect. The fuzzing framework uses the hash that was generated to determine if a crash is unique. Microsoft's !exploitable Crash Analyzer debugger extension analyzes any crashes and assigns them each a hash identifier. The fuzzer takes a starting, or "seed," file, mutates it, and opens it using the target application while monitoring that application for a crash. I used a Python-based mutational fuzzing framework for Microsoft Windows. Fuzz testing can be used as one measure of the number of vulnerabilities that an application may contain. Depending on the specific circumstances of a crash, these bugs may also result in vulnerabilities that allow an attacker to execute arbitrary code. Every bug that results in a crash has the potential of being a vulnerability. Also included are some other aspects of the Office suites that can affect the software's security.įuzz testing is a dynamic software testing technique that can be used to find bugs that result in the crashing of an application. This blog entry contains the results from a similar test that I performed in November 2010. Recently, Dan Kaminsky published a blog entry that compared the fuzzing resiliency of Microsoft Office and Oracle OpenOffice.
0 kommentar(er)
