Bug #79509 [Opn->Dup]: Segfault on wsdl tmp files from different architecture
| From: | cmb@php.net | Date: | Thu, 23 Apr 2020 07:50:09 +0000 |
| Subject: | Bug #79509 [Opn->Dup]: Segfault on wsdl tmp files from different architecture | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-226725@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=79509&edit=1
ID: 79509
Updated by: cmb@php.net
Reported by: brunni at netestate dot de
Summary: Segfault on wsdl tmp files from different
architecture
-Status: Open
+Status: Duplicate
Type: Bug
Package: SOAP related
Operating System: Linux
PHP Version: 7.2.30
-Assigned To:
+Assigned To: cmb
Block user comment: N
Private report: N
New Comment:
Duplicate of bug #70951.
Previous Comments:
------------------------------------------------------------------------
[2020-04-22 22:58:30] brunni at netestate dot de
Two more things:
-Is the serialization involved supposed to be secure? If yes you have a bigger problem.
-As the file names seem to be predictable: Is file ownership checked before using a file? If no I
can apparently crash other users PHP interpreters.
------------------------------------------------------------------------
[2020-04-22 20:18:06] brunni at netestate dot de
Description:
------------
I just spent 6.5 hours tracing a segmentation fault in PHP. The SOAP module in my new 64bit PHP was
trying to read an architecture dependent binary file named /tmp/wsdl-www-00... apparently generated
weeks earlier by my old 32bit PHP - and crashed over and over. Once I deleted all /tmp/wsdl-* files,
all was fine.
I don't think it's a good idea not to use architecture information like compile time when
generating those temporary files. I'm also not sure it's a good idea to let them lie
around in /tmp and reuse them weeks later.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=79509&edit=1