[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44319AA0.5010503@album.co.nz>
Date: Tue, 04 Apr 2006 09:58:56 +1200
From: Jasper Bryant-Greene <jasper@...um.co.nz>
To: Moriyoshi Koizumi <moriyoshi@...wakwak.com>
Cc: Tõnu Samuel <tonu@....ee>, Stefan Esser <sesser@....net>,
bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: Critical PHP bug - act ASAP if you are running
web with sensitive data
Moriyoshi Koizumi wrote:
> Jasper Bryant-Greene wrote:
>
>> I very much doubt there are many applications at all containing code
>> like this. It is illogical to be decoding html entities from user
>> input. Therefore I would not call this a "very serious problem" and
>> certainly not a critical bug.
>
> Not really. While this is not part of the HTML / HTTP standards, major
> browsers
> around try to send such characters in the user input as HTML entities
> that cannot
> all be represented in the encoding of the originating HTML page, it's
> quite probable
> the function is used to filter the query strings.
Indeed, it probably is, but hopefully the results of that are not then
echoed out to the browser without running htmlspecialchars() etc on
them... If they are (which is the root of this "security problem") then
that is the fault of the idiot who wrote the code, not PHP. You can only
protect users from their own stupidity to a certain degree...
--
Jasper Bryant-Greene
General Manager
Album Limited
http://www.album.co.nz/ 0800 4 ALBUM
jasper@...um.co.nz 021 708 334
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists