You need to log in before you can comment on or make changes to this bug.
Created an attachment (id=849) [details] ASAN Reports and crashing inputs for 4.0.9-4ubuntu1 and 47be9914ddba71eef9617cbb6656194228846228 Dear all, after reporting the following bugs to the Ubuntu security team (https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1762418), we were ask to report them directly to the libtiff developers: Dear all, The following tiff2ps memory issues were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs, each ASAN report and each ASAN report in "halt_on_error=false" mode to this bug report. To reproduce those memory issues, execute an ASAN build of tiff2ps with the crashing inputs as the first argument (./tiff2ps <crashing_input>). We can verify those issues for 4.0.9-4ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source tiff") as well as on the build based on the current gitlab commit (47be9914ddba71eef9617cbb6656194228846228). All issues are not related to http://bugzilla.maptools.org/show_bug.cgi?id=2687. However, one of our findings seems to be related to (http://bugzilla.maptools.org/show_bug.cgi?id=2754). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-Universität Bochum) Best regards, Sergej Schumilo
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets, such as this one, have been migrated to the libtiff GitLab instance at https://gitlab.com/libtiff/libtiff/issues . The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is the initial Bugzilla issue number.
