Re: Resolution for ver_export()/addslashes() encoding based script execution attack?

From: Date: Mon, 24 Feb 2014 11:07:05 +0000
Subject: Re: Resolution for ver_export()/addslashes() encoding based script execution attack?
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-72791@lists.php.net to get a copy of this message
On Mon, Feb 24, 2014 at 10:41 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote: > Hi all, > > Since this RFC is declined, > > https://wiki.php.net/rfc/multibyte_char_handling > > We need another short term resolution for it at least. > Any suggestions? > Quoting from another thread: > I'd like to start off by saying that I disagree with your premise that this is a security vulnerability that needs to be fixed quickly and across all supported versions. As far as I can see the issue is somebody using addslashes() in an inappropriate context - this is a vulnerability in the application, not PHP. This is a lot like saying that we have an RCE vulnerability in eval() because someone had the genius idea of putting eval($_GET['str']) in his or her code. There is no vulnerability here as far as PHP is concerned. As such there is no need for a short term resolution. Nikita

« previous php.internals (#72791) next »