Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 26 Mar 2012 10:06:33 +0200
From: Ludwig Nussel <>
Subject: Re: CVE-Request taglib vulnerabilities

Zubin Mithra wrote:
> On Wed, Mar 21, 2012 at 10:49 PM, Kurt Seifried <>wrote:
>> On 03/21/2012 09:42 AM, Ludwig Nussel wrote:
>>> Zubin Mithra wrote:
>>>> [...]
>>>> The issues which are present in the latest "release" but not in the
>> current
>>>> development head were :-
>>>> [3] Lack of sanity checks of fields which were read, and were used for
>>>> allocating memory; crafted files would lead of application crash.
>>> Not an issue according to upstream:
>> Shouldn't it simply say "file to large" or "unable to allocate blah"
>> something rather than crashing? I assume by "large" file the file
>> doesn't actually need to be large, just the header information needs to
>> claim it is large?
> Yes, the file does not need to be large, it just needs to have a crafted
> header.
> On investigating the issue further, discussing with a developer Lukas
> Laninsky and providing PoC's, we had confirmed that the root issue was an
> Integer overflow - which would cause a large allocation and crash the
> application.
> The changeset that corrects it can be found here =>
>>>> [4] A one bit change in a working ogg file would cause a thread to loop
>>>> infinitely.
>> Has this been confirmed? Does the looping thread actually cause a DoS,
>> simply slow down the application a bit, or?
> Yes, it just causes a thread to cause an infinite loop and does not cause
> an application crash.

So both issues qualify as security issue and CVE assignment then, right?


 (o_   Ludwig Nussel
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend├Ârffer, HRB 16746 (AG N├╝rnberg) 

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.