Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72851 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17593 invoked from network); 27 Feb 2014 23:09:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2014 23:09:03 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.49 mail-la0-f49.google.com Received: from [209.85.215.49] ([209.85.215.49:42334] helo=mail-la0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 37/B3-33117-E85CF035 for ; Thu, 27 Feb 2014 18:09:03 -0500 Received: by mail-la0-f49.google.com with SMTP id mc6so2163507lab.36 for ; Thu, 27 Feb 2014 15:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=jBZhyQtvZfghmF5yXWTZRwilNbCDbRDAhiz0V9IX3Dc=; b=lH6938RvGojI+y0vHfiSsZe6V3pVZXcoRFeF1wUYkWnb3bUKqyqt99aRj/wQQr97LW W1WyVwdqDU0PG4gFqV7NwoZ3yQ0JaMQ8kuYmnmZNXnufMoSmHea7ZWP/cyc35v2dTZB9 5jgVpuSucUzRuXhxngUJF8r86gTjwSJg3HNTGZN8eit8p4Qtsbqe2vbJfe3a735MWo7X Qz8VytULqShUe33CWuuktoDmN8uI1aSgm+U2i6uD2rUAlVwLvoV2jtDCDC68X5FBEjI/ I2AkMvAiC2VpOhE7YKhvlRJn0J/sEvmgYRnbVPg8INNAGrpQm34YC1k3RvIf8kLGbhzb ovPA== X-Received: by 10.112.56.237 with SMTP id d13mr8148256lbq.2.1393542539672; Thu, 27 Feb 2014 15:08:59 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.102 with HTTP; Thu, 27 Feb 2014 15:08:19 -0800 (PST) In-Reply-To: References: <530C3C7B.8080907@sugarcrm.com> <530C77F8.2060809@sugarcrm.com> <1393328380.5233.45.camel@guybrush> <530DADC7.2070302@lsces.co.uk> <530DDEC6.9010901@lsces.co.uk> Date: Fri, 28 Feb 2014 08:08:19 +0900 X-Google-Sender-Auth: 4gu9734TKxDRy98_inhvFftZpX8 Message-ID: To: =?UTF-8?Q?P=C3=A1draic_Brady?= Cc: Lester Caine , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1133a9220e808a04f36b68c5 Subject: Re: [PHP-DEV] Resolution for ver_export()/addslashes() encoding based script execution attack? From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a1133a9220e808a04f36b68c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Padraic, On Fri, Feb 28, 2014 at 7:22 AM, P=C3=A1draic Brady wrote: > On 26 February 2014 22:28, Yasuo Ohgaki wrote: > >> I don't see how the RFC addressed the problem anyway. > > > > Please research how databases were fixed this issue many years ago. I > don't > > remember well, but I guess it was around 2005. > > I have a vague recollection of issues, but since there's little > specific detail on this (as it pertains to PHP) publicly it's > impossible for most of us to assess what the problem may be. It's even > stranger to see a secret security report being RFC'd publicly, with > Right. This kind of discussion should be done in closed list. > the attendant discussions on list, which appears to go against > responsible disclosure if one can put two and two together in a Eureka > moment. It just spreads a lot of doubt and confusion to no end. For the time being, I suggest look for the details of char encoding based SQL/JavaScript injections. The basic is the same. Regards, P.S. Are we really going to discuss this kind of discussion in public? Can't we just discuss implementation? -- Yasuo Ohgaki yohgaki@ohgaki.net --001a1133a9220e808a04f36b68c5--