Bug #77432 [Ver]: Segmentation fault on including phar file

From: Date: Wed, 23 Jan 2019 13:13:27 +0000
Subject: Bug #77432 [Ver]: Segmentation fault on including phar file
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-219153@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=77432&edit=1 ID: 77432 Updated by: mike@php.net Reported by: tarunkant05 at gmail dot com Summary: Segmentation fault on including phar file Status: Verified Type: Bug Package: PHAR related Operating System: Linux PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Related to bug #70417 Previous Comments: ------------------------------------------------------------------------ [2019-01-23 13:12:40] mike@php.net Caused by the fix for #70417 ------------------------------------------------------------------------ [2019-01-21 11:50:09] tarunkant05 at gmail dot com Hey, but the impact of this vuln should be taken into consideration. As I elaborated the impact, it is severe. ------------------------------------------------------------------------ [2019-01-21 01:56:58] stas@php.net The problem seems to be occurring because first include closes phar's file stream, but the structure remains in phar_fname_map cache, and is loaded on the second open, but the closed FP is not reopened. Not sure what would be the proper fix though, need someone who knows phar better. ------------------------------------------------------------------------ [2019-01-12 18:24:47] tarunkant05 at gmail dot com Changed the Summary to the exact point because of that it is happening. ------------------------------------------------------------------------ [2019-01-11 17:04:30] tarunkant05 at gmail dot com Basically, Null pointer dereference is taking place in the _php_stream_seek. I think this happens because the php_stream that the _php_stream_seek function is trying to access was closed afer the first include. ------------------------------------------------------------------------ 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=77432 -- Edit this bug report at https://bugs.php.net/bug.php?id=77432&edit=1

« previous php.bugs (#219153) next »