full-disclosure - Security Advisory - phpBB 2.0.15 PHP-code injection bug

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] [day] [month] [year] [list]

Message-ID: <6170a5450506290641395b5325@mail.gmail.com>
Date: Wed Jun 29 14:41:50 2005
From: tatercrispies at gmail.com (Tatercrispies)
Subject: Security Advisory - phpBB 2.0.15 PHP-code
	injection bug

Why is this ability even present in PHP's regular expression
functions? What kind of decision making concludes that regular
expression functions should be able to execute inline code? I just
can't get my head around this.

Are there any other PHP functions that bizarrely mate EVAL ability
with seemingly unrelated functions?

> 
> The highlighting code uses the preg_replace() function on line 1110
> in viewtopic.php. It uses the special modifier "e" which causes PHP
> to evaluate the replacement string as PHP code. Below is a PHP code
> example of what actually happens:
>