Thanks for the fix. On Sat, Jan 13, 2018 at 2:18 PM, Bob Friesenhahn bfriesen@users.sf.net wrote: status: open --> closed-fixed private: Yes --> No Comment: This problem is fixed by Mercurial changeset 15332:52a91ddb1aa6. Thank you very much for reporting it. [bugs:#541] https://sourceforge.net/p/graphicsmagick/bugs/541/ Infinite Loop in ReadBMPImage (coders/bmp.c)* Status: closed-fixed Group: v1.0_(example) Created: Sat Jan 13, 2018 03:37 AM UTC by Probe Fuzzer Last Updated: Sat Jan 13, 2018 06:30...
Thanks for the fix.
Infinite Loop in ReadBMPImage (coders/bmp.c)
Thanks for your reply. We have checked the issue carefully and found it is a bug in libtiff, which got fixed in the latest version of libtiff. Thanks again.
Thanks for your work. It is a 64-bt build with address sanitizer enables (CFLAGS=-fsanitize=address). I have git pull the latest commit of libtiff and libjpeg and place the code in tiff and jpeg folders of graphicmagick source code. After complication, I can still reproduce this issue. Did you complie with address sanitizer enabled (i.e., CFLAGS=-fsanitize=address)? You said that you saw libtiff making two security-related corrections to the TIFF parsing. Could you please send me the references URL...
gm: heap-buffer-overflow in ReadTIFFImage (src/coders/tiff.c)