Search...

phpLDAPadmin <= 1.2.1.1 (query_engine) Remote PHP Code Injection Exploit

2011-11-06T00:00:00
ID SECURITYVULNS:DOC:27266
Type securityvulns
Reporter Securityvulns
Modified 2011-11-06T00:00:00

Description

phpLDAPadmin <= 1.2.1.1 (query_engine) Remote PHP Code Injection Exploit

author...............: EgiX mail.................: n0b0d13s[at]gmail[dot]com software link........: http://phpldapadmin.sourceforge.net/ affected versions....: from 1.2.0 to 1.2.1.1

[-] vulnerable code in /lib/functions.php

  1. function masort(&$data,$sortby,$rev=0) {
  2. if (defined('DEBUG_ENABLED') && DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
  3. debug_log('Entered (%%)',1,0,FILE,LINE,METHOD,$fargs);

  5. if the array to sort is null or empty

  6. if (! $data) return;
  8. static $CACHE = array();
  10. if (empty($CACHE[$sortby])) {
  11. $code = "\$c=0;\n";
  13. foreach (explode(',',$sortby) as $key) {
  14. $code .= "if (is_object(\$a) || is_object(\$b)) {\n";
  16. $code .= " if (is_array(\$a->$key)) {\n";
  17. $code .= " asort(\$a->$key);\n";
  18. $code .= " \$aa = array_shift(\$a->$key);\n";

..

  1. $code .= 'return $c;';
  3. $CACHE[$sortby] = create_function('$a, $b',$code);
  4. }

The $sortby parameter passed to 'masort' function isn't properly sanitized before being used in a call to create_function() at line 1080, this can be exploited to inject and execute arbitrary PHP code. The only possible attack vector is when handling the 'query_engine' command, here input passed through $_REQUEST['orderby'] is passed as $sortby parameter to 'masort' function.

[-] Disclosure timeline:

[30/09/2011] - Vulnerability discovered [02/10/2011] - Issue reported to http://sourceforge.net/support/tracker.php?aid=3417184 [05/10/2011] - Fix committed: http://phpldapadmin.git.sourceforge.net/git/gitweb.cgi?p=phpldapadmin/phpldapadmin;h=76e6dad [23/10/2011] - Public disclosure

[-] Proof of concept:

http://www.exploit-db.com/exploits/18021/

JSON Vulners Source
Initial Source


All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.If you are an owner of some content and want it to be removed, please mail to content@vulners.com Vulners, 2018
Protected by