Bug #77544 [Dup]: stack-buffer-overflow while using eval in php 5.6.40
| From: | insi_2304 at ymail dot com | Date: | Wed, 30 Jan 2019 17:48:27 +0000 |
| Subject: | Bug #77544 [Dup]: stack-buffer-overflow while using eval in php 5.6.40 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-219302@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=77544&edit=1
ID: 77544
User updated by: insi_2304 at ymail dot com
Reported by: insi_2304 at ymail dot com
Summary: stack-buffer-overflow while using eval in php 5.6.40
Status: Duplicate
Type: Bug
Package: Scripting Engine problem
Operating System: Kali Linux
PHP Version: 5.6.40
Block user comment: N
Private report: N
New Comment:
The bug status should be anything other than duplicate as the bug#70430 was fixed in 2015 itself. I
think it is different code path in the Zend language parser that is why it is still present in the
5.6.40 for which the release date is 10-jan-2019.
Previous Comments:
------------------------------------------------------------------------
[2019-01-30 15:13:13] nikic@php.net
PHP 5.6 is EOL, so it will not be fixed there, no. You are right though that PHP 5.6 and PHP 7.0
probably shouldn't appear on the download page anymore.
@cmb: Maybe you know how to do that?
------------------------------------------------------------------------
[2019-01-30 15:03:09] insi_2304 at ymail dot com
Shouldn't it be fixed in 5.6.40 as it is being provided on main website, not even in the
archive downloads to download it and this was the reason why I started testing it
------------------------------------------------------------------------
[2019-01-30 14:53:57] nikic@php.net
This is bug #70430, which has been fixed in PHP 7.0.
------------------------------------------------------------------------
[2019-01-30 14:44:24] insi_2304 at ymail dot com
Will this one be fixed?
------------------------------------------------------------------------
[2019-01-30 12:04:24] cmb@php.net
Then we likeley should cater to these memory leaks first.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=77544
--
Edit this bug report at https://bugs.php.net/bug.php?id=77544&edit=1