full-disclosure - Fuzzing Microsoft Office

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <200607111329.k6BDTFkp004189@turing-police.cc.vt.edu>
Date: Tue Jul 11 14:29:24 2006
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Fuzzing Microsoft Office

On Tue, 11 Jul 2006 13:52:49 BST, Disco Jonny said:

> mate if you care, or give a shit.  I have over 300 *different* crashes
> in word ( total over 5k files that crash word), from using two basic
> templates and then fuzzing them

Out of curiosity, how do you determine conclusively that they're in fact
different crashes, rather than just different symptoms of the same problem?

For instance, a bounds check on string A that trashes memory - can manifest
as almost *anything*, as it depends on what the *next* thing in memory is, and
when/how it gets dereferenced.  This is particularly an issue when it's heap
corruption.  If the previous sentence had 2 bold strings, then thing B on
the heap gets splatted, causing one crash, but if there's an italic string,
then it's C that gets trashed, causing a different manifestation.

It's still the same bug with A though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060711/c4657921/attachment.bin