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

From: Date: Thu, 31 Jan 2019 13:41:22 +0000
Subject: Bug #77432 [Com]: Segmentation fault on including phar file
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-219310@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
 Comment by:         tarunkant05 at gmail dot com
 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:

Is there any update on the same?


Previous Comments:
------------------------------------------------------------------------
[2019-01-23 16:49:57] cmb@php.net

It seems to me we have to revert commit 995ecff[1].

[1] <http://git.php.net/?p=php-src.git;a=commit;h=995ecffbb2ef972c2d01200ee15b39feb7c6d066>

------------------------------------------------------------------------
[2019-01-23 13:13:27] mike@php.net

Related to bug #70417

------------------------------------------------------------------------
[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.

------------------------------------------------------------------------


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


Thread (1 message)

  • tarunkant05 at gmail dot com
  • Unknown Message
    • tarunkant05 at gmail dot com
« previous php.bugs (#219310) next »