Closed
Description
Description of problem:
A heap-based buffer overflow Read in RemoveUnknownSections in jpgfile.c
Version-Release number of selected component (if applicable):
I tested the following version:
Jhead version: 3.05
Jhead version: 3.04
How reproducible:
git clone --depth=1 https://github.com/Matthias-Wandel/jhead.git && cd jhead && make CC="clang" -e CFLAGS="-g -fsanitize=address" -e LDFLAGS="-g -fsanitize=address"
Steps to Reproduce:
1.just run the following command
./jhead -purejpg ./tests_61787.jpg
poc:tests_61787.zip
Actual results:
AddressSanitizer Report
$ ./jhead -purejpg ./tests_61787.jpg
Nonfatal Error : './tests_61787.jpg' Extraneous 10 padding bytes before section C4
=================================================================
==26268==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60e0000000e0 at pc 0x000000494f5f bp 0x7ffead788260 sp 0x7ffead787a28
READ of size 80 at 0x60e0000000e0 thread T0
#0 0x494f5e in __asan_memmove (/root/fuzz/jhead/test/jhead+0x494f5e)
#1 0x4d172e in RemoveUnknownSections /root/fuzz/jhead/jpgfile.c:718:17
#2 0x4ca6d4 in ProcessFile /root/fuzz/jhead/jhead.c:1182:13
#3 0x4c74e5 in main /root/fuzz/jhead/jhead.c:1759:13
#4 0x7fc36297383f in __libc_start_main /build/glibc-e6zv40/glibc-2.23/csu/../csu/libc-start.c:291
#5 0x41b858 in _start (/root/fuzz/jhead/test/jhead+0x41b858)
0x60e0000000e0 is located 0 bytes to the right of 160-byte region [0x60e000000040,0x60e0000000e0)
allocated by thread T0 here:
#0 0x4959c9 in realloc (/root/fuzz/jhead/test/jhead+0x4959c9)
#1 0x4cf59f in CheckSectionsAllocated /root/fuzz/jhead/jpgfile.c:107:33
#2 0x4ce3c0 in ReadJpegSections /root/fuzz/jhead/jpgfile.c:139:9
#3 0x4cfd96 in ReadJpegFile /root/fuzz/jhead/jpgfile.c:381:11
#4 0x4c8850 in ProcessFile /root/fuzz/jhead/jhead.c:908:10
#5 0x4c74e5 in main /root/fuzz/jhead/jhead.c:1759:13
#6 0x7fc36297383f in __libc_start_main /build/glibc-e6zv40/glibc-2.23/csu/../csu/libc-start.c:291
SUMMARY: AddressSanitizer: heap-buffer-overflow (/root/fuzz/jhead/test/jhead+0x494f5e) in __asan_memmove
Shadow bytes around the buggy address:
0x0c1c7fff7fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff7fd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff7fe0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff7ff0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8000: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
=>0x0c1c7fff8010: 00 00 00 00 00 00 00 00 00 00 00 00[fa]fa fa fa
0x0c1c7fff8020: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8030: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8040: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8050: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8060: 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
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
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
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==26268==ABORTING
Additional info:
Founder: giantbranch of NSFOCUS Security Team
Metadata
Metadata
Assignees
Labels
No labels