Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-04-09 Thread Moriyoshi Koizumi
Peter Conrad wrote: Hi, On Mon, Apr 03, 2006 at 11:06:01PM +0900, Moriyoshi Koizumi wrote: 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 origin

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-04-05 Thread Jasper Bryant-Greene
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 r

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-04-04 Thread John Bond
On 3/29/06, Jeff Rosowski <[EMAIL PROTECTED]> wrote: > It also doesn't affect all versions of PHP. on 5.0.5, it returns \0 > followed by however many Ss you put after it. And your right you wouldn't > trust user imput like that. > > ___ I get this beha

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-04-04 Thread Jasper Bryant-Greene
Jasper Bryant-Greene wrote: 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 certainl

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-04-04 Thread Moriyoshi Koizumi
Jasper Bryant-Greene wrote: Tõnu Samuel wrote: Nice! I was really nervous already as I got bombed with e-mails and I really did not knew much more than was discovered. Meanwhile I am bit disappointed that we had nearly month such a bug in wild and software distributors like SuSE in my cas

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-03-31 Thread Jeff Rosowski
really did not knew much more than was discovered. Meanwhile I am bit disappointed that we had nearly month such a bug in wild and software distributors like SuSE in my case did not published patches. I think as long enough time passed and I hope distributors maybe need to see it - I publish e

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-03-29 Thread Tõnu Samuel
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. Somewhat I agree. I suspected this may affect more function

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-03-29 Thread Jasper Bryant-Greene
Tõnu Samuel wrote: Nice! I was really nervous already as I got bombed with e-mails and I really did not knew much more than was discovered. Meanwhile I am bit disappointed that we had nearly month such a bug in wild and software distributors like SuSE in my case did not published patches. I

Re: [Full-disclosure] Critical PHP bug - act ASAP if you are running web with sensitive data

2006-03-28 Thread Stefan Esser
Hello, just to stop this: The bug is a binary safety issue in html_entity_decode. A function that is not usually used on user input, because user input is usually not expected in HTML format and then decoded. Even if the function is used on user input it can only leak memory to a potential attack