Sec Bug->Bug #73164 [Opn]: crash in zend_new_interned_string_int when include PHAR file
| From: | stas@php.net | Date: | Thu, 20 Oct 2016 02:29:06 +0000 |
| Subject: | Sec Bug->Bug #73164 [Opn]: crash in zend_new_interned_string_int when include PHAR file | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-204929@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=73164&edit=1
ID: 73164
Updated by: stas@php.net
Reported by: nguyenluan dot vnn at gmail dot com
Summary: crash in zend_new_interned_string_int when include
PHAR file
Status: Open
-Type: Security
+Type: Bug
Package: PHAR related
PHP Version: 5.6.26
Block user comment: N
Private report: Y
Previous Comments:
------------------------------------------------------------------------
[2016-10-19 14:16:46] nguyenluan dot vnn at gmail dot com
Yes, I agree with you. No PHP developer could include file larger than 2Gb. But please change it to
Bug and fix it.
------------------------------------------------------------------------
[2016-10-12 00:02:51] stas@php.net
Please provide a reproducing case where it's not doing something no real PHP programmer would
do, like including 2GB zip file as PHP.
------------------------------------------------------------------------
[2016-09-26 12:25:34] nguyenluan dot vnn at gmail dot com
I tested to include a PHP with length larger than 2Gb and this still happen. I think we have problem
when include any file larger than 2Gb. This could cause PHP to crash and denial of service.
------------------------------------------------------------------------
[2016-09-26 04:41:40] stas@php.net
Doesn't look like security issue - you're including a zip file, that's not what is
commonly done.
------------------------------------------------------------------------
[2016-09-26 04:40:28] stas@php.net
Ah, sorry, didn't notice, it's at the end.
------------------------------------------------------------------------
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=73164
--
Edit this bug report at https://bugs.php.net/bug.php?id=73164&edit=1