Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 9 Oct 2016 11:28:25 +0200
From: Marcus Meissner <meissner@...e.de>
To: oss-security@...ts.openwall.com
Subject: Re: potrace: memory allocation failure

Hi,

did you attach the reproducer files somewhere?

Ciao, Marcus
On Sat, Oct 08, 2016 at 10:30:54PM +0200, Agostino Sarubbo wrote:
> Description:
> potrace is a utility that transforms bitmaps into vector graphics.
> 
> A crafted image, through a fuzz testing, causes the memory allocation to fail.
> 
> This is the first case where my ASan symbolyzer didn’t start up correctly. I’m 
> reporting only what it prints at the end (not useful at all but demostrates a 
> bit that the issue exist)
> 
> # potrace $FILE
> potrace: warning: 2.hangs: premature end of file
> ==13660==ERROR: AddressSanitizer failed to allocate 0x200003000 (8589946880) 
> bytes of LargeMmapAllocator (error code: 12)
> ==13660==AddressSanitizer CHECK failed: /var/tmp/portage/sys-
> devel/llvm-3.8.1/work/llvm-3.8.1.src/projects/compiler-
> rt/lib/sanitizer_common/sanitizer_common.cc:183 "((0 && "unable to mmap")) != 
> (0)" (0x0, 0x0)
> 
> Affected version:
> 1.13
> 
> Fixed version:
> N/A
> 
> Commit fix:
> N/A
> 
> Credit:
> This bug was discovered by Agostino Sarubbo of Gentoo.
> 
> CVE:
> N/A
> 
> Timeline:
> 2016-08-26: bug discovered
> 2016-08-27: bug reported privately to upstream
> 2016-08-29: blog post about the issue
> 
> Note:
> This bug was found with American Fuzzy Lop.
> 
> Permalink:
> https://blogs.gentoo.org/ago/2016/08/29/potrace-memory-allocation-failure/
> 
> 

-- 
Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real <meissner@...e.de>

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.