Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101115
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 as permitted sender)
MIME-Version: 1.0
Sender: giovanni.g@gmail.com
In-Reply-To: <eabb8265-c82b-16da-82af-e9d9669fe7ac@cubiclesoft.com>
References: <CAESVnVodb3=ANb-5ZY5p5_SpLsbE7JQJ7+BEzmX-A8U=TbBYnw@mail.gmail.com>
 <eabb8265-c82b-16da-82af-e9d9669fe7ac@cubiclesoft.com>
Date: Thu, 9 Nov 2017 19:07:06 +0100
Message-ID: <CAML1Pf7_WZJOo3Hma7Qdi3wztoi6RNw_C-YmNRJaL54r7n5SjA@mail.gmail.com>
To: Thomas Hruska <thruska@cubiclesoft.com>
Cc: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="f40304363e280f7747055d90ac00"
Subject: Re: [PHP-DEV] PHP 7.2.0 RC6 Released
From: giovanni@giacobbi.net (Giovanni Giacobbi)

--f40304363e280f7747055d90ac00
Content-Type: text/plain; charset="UTF-8"

On 9 November 2017 at 18:46, Thomas Hruska <thruska@cubiclesoft.com> wrote:

> On 11/9/2017 7:36 AM, Sara Golemon wrote:
>
>> The sixth (and likely final) release candidate for 7.2.0 was just
>> released and can be
>> downloaded from:
>> https://downloads.php.net/~pollita/
>> Or using the git tag: php-7.2.0RC6
>>
>> Barring unforeseen calamity, everyone should expect 7.2.0-final on
>> Thursday, November 30th.
>>
>
> Issue #73535?  I consider letting a known security vulnerability that goes
> largely unaddressed but persists into the next major version of a software
> product to be quantifiable as a calamity of sorts.  It's fast approaching a
> full year without any resolution in sight.  Many people would have zero
> day-ed the issue by this point at whatever conferences have come and gone
> (Black Hat, DEF CON, etc.) to grab some quick notoriety.  I don't believe
> that zero day-ing a vulnerability on a stage is the right solution for a
> garden variety of reasons.
>
>
This is utterly disappointing considering that bug #73535 is marked as
private and I couldn't easily gather more information about this bug on
google. Since I have the feeling this is an open secret can you disclose
more information and proposed patches so that sysadmins can assess by
themselves the risks, mitigation techniques, and whether to patch their own
installations?

I guess the dev team wouldn't leave us with our pants down, so I expect
this to of difficult exploitability. Anyway, after a year it's time for
full disclosure, don't you think?

Kind regards
GG

--f40304363e280f7747055d90ac00--