|
|
BugTraq
Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Mar 29 2006 03:22AM Jasper Bryant-Greene (jasper album co nz) (3 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Apr 03 2006 02:06PM Moriyoshi Koizumi (moriyoshi at wakwak com) (1 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Mar 29 2006 04:43PM Jeff Rosowski (rosowskij ie ymp gov) (1 replies) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Apr 04 2006 01:29PM John Bond (john r bond gmail com) Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data Mar 29 2006 05:19AM Tõnu Samuel (tonu jes ee) |
|
Privacy Statement |
> 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 (at) album.co (dot) nz [email concealed] 021 708 334
[ reply ]