Hi,
I did a quick run with american fuzzy lop on libabw and it found the
attached crasher.
Attached both sample exposing segfault and asan/valgrind output. It's
an invalid memory read access.
As here are a lot of people working on import filters: These are very
suspectible to these type of
On Sun, 21 Dec 2014 12:57:03 +1100
Chris Sherlock chris.sherloc...@gmail.com wrote:
Do you have any instructions on how you went about doing that?
I've finished now the three-part tutorial for the fuzzing project, you
may find that helpful:
https://fuzzing-project.org/tutorial1.html
If you
List of changes:
- Use symbol visibility on Linux. The library only exports the two public
functions now.
- Handle text language.
- Honor global setting of writing mode.
- Handle basic document metadata.
- Handle headings.
- Fix the loss of text formatting attributes that would happen in
Hi,
On Sat, Dec 20, 2014 at 05:44:50PM +0100, Hanno Böck wrote:
Hi,
I did a quick run with american fuzzy lop on libabw and it found the
attached crasher.
Attached both sample exposing segfault and asan/valgrind output. It's
an invalid memory read access.
This has already been found by
|Excelent!!
https://github.com/cyberthrone/
https://launchpad.net/~alfierimorillo
Ubuntu User number is # 35087
Public profile linux for user #97
alfieri.mori...@libreoffice-ve.net
Web Master libreoffice-ve http://libreoffice-ve.org/ y Gimp-ve
http://gimp-ve.com/
Do you have any instructions on how you went about doing that?
Chris
Sent from my iPhone
On 21 Dec 2014, at 4:34 am, David Tardon dtar...@redhat.com wrote:
I know... I used zzuf on some of our libs in the past. And I have been
using afl since I discovered it 4-5 weeks ago. I have already
