Heap buffer overflow in tiffcp.c:948
Summary There is a heap buffer overflow in tools/tiffcp.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted tiff file. Version LIBTIFF, Version 4.3.0, commit id fb61aee88af047a727dd9aefeb7096c075b61581 POC file [heap-buffer-overflow_tiffcp.c-948](/uploads/9c5dbbe5c1da52b7d5ab09db464c8139/heap-buffer-overflow_tiffcp.c-948) [poc_tiffcp_948](/uploads/34800cee61d37337836777081852733d/poc_tiffcp_948) Steps to reproduce ``` # export CFLAGS="-O -g -fsanitize=address" # export CXXFLAGS="-O -g -fsanitize=address" # ./configure --prefix=$PWD/build_asan # make -j64 & make install # ./build_asan/bin/tiffcp poc /tmp/foo TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order. poc2: Warning, Nonstandard tile width 1, convert file. TIFFFetchStripThing: Warning, Incorrect count for "StripOffsets"; tag ignored. TIFFFetchStripThing: Warning, Incorrect count for "StripByteCounts"; tag ignored. ================================================================= ==115545==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000ef9f at pc 0x7efffaa8b20b bp 0x7ffea9d01d20 sp 0x7ffea9d014c8 READ of size 1 at 0x60200000ef9f thread T0 #0 0x7efffaa8b20a in __interceptor_strlen (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x7020a) #1 0x406f98 in tiffcp /root/programs/Libtiff/tools/tiffcp.c:948 #2 0x406f98 in main /root/programs/Libtiff/tools/tiffcp.c:334 #3 0x7efffa33e83f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f) #4 0x401ab8 in _start (/root/programs/Libtiff/build_asan/bin/tiffcp+0x401ab8) 0x60200000ef9f is located 0 bytes to the right of 15-byte region [0x60200000ef90,0x60200000ef9f) allocated by thread T0 here: #0 0x7efffaab3602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7efffa7bbc61 in _TIFFmalloc /root/programs/Libtiff/libtiff/tif_unix.c:314 SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 __interceptor_strlen Shadow bytes around the buggy address: 0x0c047fff9da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9dd0: fa fa fa fa fa fa fa fa fa fa 02 fa fa fa fd fa 0x0c047fff9de0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa =>0x0c047fff9df0: fa fa 00[07]fa fa fd fd fa fa 02 fa fa fa 00 00 0x0c047fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9e30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9e40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe ==115545==ABORTING ``` Platform ``` # uname -a Linux 37d1a8efe7bb 4.15.0-142-generic #146~16.04.1-Ubuntu SMP Tue Apr 13 09:27:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ```
issue