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]

Date: Wed Mar 29 08:16:35 2006
From: tonu at jes.ee (Tõnu Samuel)
Subject: Critical PHP bug - act ASAP if you are running
	web with sensitive data

Slythers Bro wrote:

> <?php
>    $host = "127.0.0.1 <http://127.0.0.1>";
>    $user = "sqluser";
>    $pass = "sqlpass";
>
>    $foobar=html_entity_decode($_GET['foo']);
>    echo $foobar;
>
> ?>

Situation is worse. I was able to see

1. Source code itself (may expose bugs in software)
2. Data from other threads. For exaxmple on busy web server I see pieces 
of HTML other users are seeing. Think if they are watching their private 
e-mails or use internet banking.

What is good for attacker - this exploit does not crash server. Just 
"reload" and more data is coming. So try it on production server and you 
see how dangerous it might be. At least till now we got no crashing 
problems with it.

    T?nu