full-disclosure - Critical PHP bug - act ASAP if you are running web with sensitive data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060329084055.H59763@infeng.ymp.gov>
Date: Wed Mar 29 17:43:36 2006
From: rosowskij at ie.ymp.gov (Jeff Rosowski)
Subject: Critical PHP bug - act ASAP if you are running
	web with sensitive data

>> 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 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.