On Wed, Mar 21, 2012 at 10:49 PM, Kurt Seifried <kseifried () redhat com>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
development head were :-
 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
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
The changeset that corrects it can be found here =>
 A one bit change in a working ogg file would cause a thread to loop
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.