Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15780 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13624 invoked by uid 1010); 4 Apr 2005 04:50:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13609 invoked from network); 4 Apr 2005 04:50:56 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 4 Apr 2005 04:50:56 -0000 X-Host-Fingerprint: 64.233.184.198 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.198:28024] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id F0/84-19272-FA7C0524 for ; Mon, 04 Apr 2005 00:50:56 -0400 Received: by wproxy.gmail.com with SMTP id 57so993017wri for ; Sun, 03 Apr 2005 21:50:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PjUuGZ/tuvwxQbTyM1uLIBcswRdW/RAYdTHgAXu4gZfCLFd+d3Mt3kh4TxmxNz4Lm44hZkM083zGeAT9uMDzrEmPzcUcbSl3/epMO9jb+tl0PPMr6d+yUXf1TJDn/yXYz+Hx4Bw6CVXVZET/TVDYcx2Y3fdjZn7wI8VocU1fSZY= Received: by 10.54.50.73 with SMTP id x73mr275727wrx; Sun, 03 Apr 2005 21:50:47 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Sun, 3 Apr 2005 21:50:47 -0700 (PDT) Message-ID: <4e89b426050403215076f5448e@mail.gmail.com> Date: Sun, 3 Apr 2005 23:50:47 -0500 Reply-To: Wez Furlong To: Mark Krenz Cc: internals@lists.php.net In-Reply-To: <20050404043233.GV32563@arvo.suso.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050404043233.GV32563@arvo.suso.org> Subject: Re: [PHP-DEV] Should I report this bug/exploit? From: kingwez@gmail.com (Wez Furlong) Please send details to security@php.net for further analysis. --Wez. On Apr 3, 2005 11:32 PM, Mark Krenz wrote: > > Hi, I've been using PHP for a long time and have recently found a > couple of major bugs that would allow pretty much any user on a shared > web hosting server to read other user's files. The conditions for this > exploit are quite common. Also, from what I can tell, this exploit > would not be very easy to fix and in fact may not be fixable until a > peruser MPM for Apache is completely ready (Like perchild or Metux). > It could be that you already know about this problem but have also not > reported it. I couldn't find any other information about it from doing > some searches. > > This leads me to wonder, is it a good idea to make this vulnerability > known? On the one hand, releasing the information would allow admins > and developers to try to fix it, but on the other hand, if its not > immediately fixable it would allow for a large window of opportunity for > attacks. Thus, I came to this list for some advice on what I should do. > Maybe I could at least email one of your privately so that you can see > what it is. > > Thanks, > > Mark > > -- > Mark S. Krenz > IT Director > Suso Technology Services, Inc. > http://suso.org/ > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >