[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimzu6AhXeTfrAkvH-l9AbtB6M7pMn_pAKynDWbw@mail.gmail.com>
Date: Wed, 30 Jun 2010 14:58:58 -0400
From: Dan Rosenberg <dan.j.rosenberg@...il.com>
To: Josh Bressers <bressers@...hat.com>
Cc: oss-security@...ts.openwall.com
Subject: Re: CVE requests: LibTIFF
There are three issues that I think are CVE-worthy and have not been assigned:
1. OOB read in TIFFExtractData() leading to crash (no reference,
originally disclosed by me in this thread, fixed upstream with release
3.9.4 and security fix backported by Ubuntu).
2. NULL pointer dereference due to invalid td_stripbytecount leading
to crash (distinct from CVE-2010-2443). The upstream changelog entry
for 3.9.4 reads:
* libtiff/tif_ojpeg.c (OJPEGReadBufferFill): Report an error and
avoid a crash if the input file is so broken that the strip
offsets are not defined.
3. OOB read in TIFFRGBAImageGet() leading to crash. Reference:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/591605
-Dan
On Wed, Jun 30, 2010 at 2:42 PM, Josh Bressers <bressers@...hat.com> wrote:
> ----- "Tomas Hoger" <thoger@...hat.com> wrote:
>
>> On Tue, 29 Jun 2010 08:05:25 -0400 Dan Rosenberg wrote:
>>
>> > On request, I'm re-posting the issues which I think actually deserve
>> > CVE ids.
>>
>> I believe the disagreement here is caused by different opinions on what
>> should be and what does not need to be called security.
>>
>
> This thread confuses me (it's not hard to do).
>
> Can someone sum up what still needs CVE ids with a reference link or two?
>
> Thanks.
>
> --
> JB
>
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
