Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 18 Oct 2016 14:06:41 +0200
From: Adam Maris <>
Subject: Re: CVE assignment for PHP 5.6.27 and 7.0.12

On 18/10/16 09:42, Lior Kaplan wrote:
> Hi,
> Please assign a CVE for the following issue:
> Bug #73147    Use After Free in unserialize()
> Thanks,
> Kaplan
16 bugs marked as 'security' were fixed in php 5.6.27 of which only one has CVE assigned.
Here you request CVE for another one issue (even the documentation says it's unsafe to use
unserialize on untrusted input).

Are you planning to obtain CVEs also for other security bugs or do you treat the rest as
CVE-unworthy? Or are reporters/community supposed to do it?


Adam Mariš, Red Hat Product Security
1CCD 3446 0529 81E3 86AF  2D4C 4869 76E7 BEF0 6BC2

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.