How to exhaust memory with one reputably sourced image about hachoir HOT 5 OPEN

On Aug 27, 2019, at 12:50 AM, Victor Stinner ***@***.***> wrote: Yeah, Hachoir has bugs, but it's basically no longer maintained: http://unmaintained.tech/ If you propose a fix, I can try to review it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

On Aug 28, 2019, at 1:55 PM, Victor Stinner ***@***.***> wrote: The problem is that Hachoir allows to create 2 fields at the same address: + 0) start_image: Start of image (SOI) (2 bytes) - 2) exif: EXIF (292 bytes) 0) header= 0xff: Header (1 bytes) 1) type= 0xe1: Type (1 bytes) 2) size= 290: Size (2 bytes) - 4) content: Chunk content (288 bytes) 0) header= "Exif\0\0": Header (Exif\0\0) (6 bytes) 6) endian= "MM": Endian ('II' or 'MM') (2 bytes) 8) version= 42: TIFF version number (2 bytes) 10) img_dir_ofs= 8: Next image directory offset (4 bytes) + 14) ifd[0] (216 bytes) + 234) exif[0] (54 bytes) + 14) ifd[1] (216 bytes) + 234) exif[1] (54 bytes) + 14) ifd[2] (216 bytes) + 234) exif[2] (54 bytes) + 14) ifd[3] (216 bytes) ... It should raise an error. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.