You need to log in before you can comment on or make changes to this bug.
Created an attachment (id=762) [details] testcase on libtiff 4.0.7 A memory leak vulnerability was found in tiff2pdf.c:808 which allows attackers to cause a denial of service via a crafted file. tiff2pdf $FILE -o out.pdf ==103057==ERROR: LeakSanitizer: detected memory leaks Direct leak of 12556 byte(s) in 1 object(s) allocated from: #0 0x7fd4b1c37f20 in __interceptor_realloc ../../../../libsanitizer/asan/asan_malloc_linux.cc:75 #1 0x507e13 in _TIFFrealloc /home/haojun/Downloads/testopensourcecode/tiff-4.0.7/libtiff/tif_unix.c:328 #2 0x410c03 in t2p_readwrite_pdf_image /home/haojun/Downloads/testopensourcecode/tiff-4.0.7/tools/tiff2pdf.c:2597 #3 0x42c71c in t2p_write_pdf /home/haojun/Downloads/testopensourcecode/tiff-4.0.7/tools/tiff2pdf.c:5549 #4 0x404386 in main /home/haojun/Downloads/testopensourcecode/tiff-4.0.7/tools/tiff2pdf.c:808 #5 0x7fd4b0e43b34 in __libc_start_main (/lib64/libc.so.6+0x21b34) SUMMARY: AddressSanitizer: 12556 byte(s) leaked in 1 allocation(s). testcase:https://github.com/bestshow/p0cs/blob/master/memory-leak-in-tiff2pdf-1.tif
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets, such as this one, have been migrated to the libtiff GitLab instance at https://gitlab.com/libtiff/libtiff/issues . The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is the initial Bugzilla issue number.
