Hi Salvatore, On Sun, Sep 27, 2015 at 8:39 AM, Salvatore Bonaccorso <[email protected]> wrote: > Source: tiff > Version: 4.0.2-6 > Severity: important > Tags: security upstream [...] > CVE-2015-7313[0]: > OOM when parsing crafted tiff files [...] > [0] https://security-tracker.debian.org/tracker/CVE-2015-7313 It seems upstream knows about it[1] for a few days and this still not fixed in the CVS; the viewpoint is: "FYI, the file has a # of image lines around four billion. I didn't dig into it closely when first reported, but it might be that auto-strip-chopping is creating an expensive/large data structure.
I'm not entirely confident whether to treat library requests for large amounts of memory as a defect in the library. It makes me sad that modern operating systems seem to have trouble just return NULL for malloc() calls for which there isn't enough memory available. (If my assumptions are correct)." I hope there will be a solution. Regards, Laszlo/GCS [1] http://seclists.org/oss-sec/2015/q3/631
