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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <44312BC9.3020407@at.wakwak.com>
Date: Mon Apr  3 16:22:38 2006
From: moriyoshi at at.wakwak.com (Moriyoshi Koizumi)
Subject: Critical PHP bug - act ASAP if you are running
	web with sensitive data

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

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.

Moriyoshi

>
> Jasper
>