|
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 Apr 03 2006 09:58PM Jasper Bryant-Greene (jasper album co nz) 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 |
>> 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 exploit. Sorry, this was discovered independently and for me it
>> looks like very serious problem.
>>
>> Script is:
>> <?php
>>
>> $foobar=html_entity_decode($_GET['foo']);
>> echo $foobar;
>>
>> ?>
>
> 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.
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.
[ reply ]