[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f576c0cf-d5dc-7451-2e89-8c8d74f660a0@redhat.com>
Date: Thu, 8 Jun 2017 15:54:27 -0600
From: Kurt Seifried <kseifried@...hat.com>
To: oss-security@...ts.openwall.com, Glenn Randers-Pehrson <glennrp@...il.com>
Subject: Re: Is not memory allocation failure a bug?
On 2017-06-08 3:04 PM, Glenn Randers-Pehrson wrote:
> I just checked a fix for one of those into Firefox yesterday. It wasn't
> considered a serious problem because the malloc would eventually
> fail safely, but it's better to predict the problem ahead of time and not
> even try to malloc all available memory.
>
> See https://bugzilla.mozilla.org/show_bug.cgi?id=1368407
> in which a tiny PNG file tries to claim Gigabytes of memory.
Ok so I tested it, no crash/huge memory thing, but the CPU got maxed and
even when I closed the tab for the image Firefox kept eating CPU, I
wasn't able to close Firefox, had to use the kill command (which worked
fine) so this clearly falls into the DoS camp and may need a CVE, has
Mozilla commented on why they have elected to NOT give it a CVE?
--
Kurt Seifried -- Red Hat -- Product Security -- Cloud
PGP A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
Red Hat Product Security contact: secalert@...hat.com
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.
