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: <44319AA0.5010503@album.co.nz>
Date: Mon Apr  3 22:59:08 2006
From: jasper at album.co.nz (Jasper Bryant-Greene)
Subject: Critical PHP bug - act ASAP if you are running
	web with sensitive data

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 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@...um.co.nz          021 708 334