WatskeBart Posted March 8, 2017 Share Posted March 8, 2017 (edited) Quote EDIT: To SSH into the BashBunny use IP: 172.16.64.1 When running the following payload: LED G ATTACKMODE RNDIS_ETHERNET And try to SSH into the bunny (172.16.64.10) with Putty. As root I always get 'Access Denied' I've change the default password using attackmode serial but that password is not working for SSH. I even set it back to the default hak5bunny password, but still no joy. What am I missing here? Edited March 9, 2017 by WatskeBart 1 Quote Link to comment Share on other sites More sharing options...
Torrey Posted March 8, 2017 Share Posted March 8, 2017 Darren used 172.16.64.1 as the address to SSH into on the latest Hak5 episode. Quote Link to comment Share on other sites More sharing options...
MrSnowMonster Posted March 8, 2017 Share Posted March 8, 2017 Did anyone of you get a working internet connection? I am trying to apt-get update, but it just continue to connect to httpredir.debian.com... root@bunny:/pentest/impacket/examples# apt-get update 0% [Connecting to httpredir.debian.org (140.211.166.202)] I think I need to update because every time I try to run rdp_check.py I get The error under: root@bunny:/pentest/impacket/examples# rdp_check.py CRITICAL:root:pyOpenSSL is not installed, can't continue Quote Link to comment Share on other sites More sharing options...
rastating Posted March 8, 2017 Share Posted March 8, 2017 1 hour ago, WatskeBart said: When running the following payload: LED G ATTACKMODE RNDIS_ETHERNET And try to SSH into the bunny (172.16.64.10) with Putty. As root I always get 'Access Denied' I've change the default password using attackmode serial but that password is not working for SSH. I even set it back to the default hak5bunny password, but still no joy. What am I missing here? 172.16.64.10 will be the IP address your host machine has been assigned. The IP address of the bunny will be 172.16.64.1 Default values from the wiki are: Username: root Password: hak5bunny IP Address: 172.16.64.1 DHCP Range: 172.16.64.10-12 2 Quote Link to comment Share on other sites More sharing options...
chairman Posted March 8, 2017 Share Posted March 8, 2017 I followed the Ethernet sharing instructions but Instead of configuring an IP of "172.16.64.64" to the IP4. I just checked "Obtain an IP address automatically" I downloaded NetPing http://netping.codeplex.com/downloads/get/11024 and had it scan 172.16.64.1 to 172.16.64.255 it found 172.16.64.1 --> BashBunny 172.16.64.10 --> my Windows 10 PC Only took me about 3 hours to find this simple solution I can now SSH to the BashBunny Quote Link to comment Share on other sites More sharing options...
chairman Posted March 9, 2017 Share Posted March 9, 2017 Ok, Followed the directions exactly. the 172.16.64.64 is the address of your PC & Gateway 172.16.64.1 is the address of the BashBunny. I then moved it to a Windows 7 PC and NOW all is working, PINGs & DNS are working. apt-get works Quote Link to comment Share on other sites More sharing options...
WatskeBart Posted March 9, 2017 Author Share Posted March 9, 2017 silly me, rookie mistake. Wrong IP indeed. 1 Quote Link to comment Share on other sites More sharing options...
chairman Posted March 9, 2017 Share Posted March 9, 2017 Anyone get this going on Windows 10? I can setup my Windows 7 laptop the same as the Windows 10 PC, Connection refused when I SSH from the 10 to the BashBunny. & no out to the Internet Same Bunny & Setup on Windows 7, no problem SSH in or Apt-get out. I figure its Windows 10 Firewall but I turned off the firewall and still no joy Quote Link to comment Share on other sites More sharing options...
WatskeBart Posted March 9, 2017 Author Share Posted March 9, 2017 (edited) 33 minutes ago, chairman said: Anyone get this going on Windows 10? I can setup my Windows 7 laptop the same as the Windows 10 PC, Connection refused when I SSH from the 10 to the BashBunny. & no out to the Internet Same Bunny & Setup on Windows 7, no problem SSH in or Apt-get out. I figure its Windows 10 Firewall but I turned off the firewall and still no joy Is your payload.txt containing: ATTACKMODE RNDIS_ETHERNET? Is the BashBunny recognized as a IBM USB Remote NDIS network device? If so, does it get a IP e.g. 172.16.64.10 (use ipconfig /all you should see IBM USB Remote NDIS Network Device in the description)? Then you should be able to SSH into 172.16.64.1 and connect to the BashBunny This works for me, and i'm using a firewall as well. Edited March 9, 2017 by WatskeBart Quote Link to comment Share on other sites More sharing options...
chairman Posted March 10, 2017 Share Posted March 10, 2017 Hmmm, I have been using the BashBunny on Windows 10 on my work laptop, wher it was not so happy. Brought it home and setup my personal Win10 laptop and all works perfect Maybe some Group Policy was fighting me. So thanks for the help, all is good Quote Link to comment Share on other sites More sharing options...
WatskeBart Posted March 10, 2017 Author Share Posted March 10, 2017 @chairman glad it worked out. Interesting though why it wouldn't work on Win10 work laptop and if so which policy is preventing this. Quote Link to comment Share on other sites More sharing options...
MetateM Posted April 27, 2017 Share Posted April 27, 2017 I am having the same issues on my windows 10 laptop as well. I tried disabling firewalls and such. It seems that as soon as you enable internet connection sharing it turns Ethernet 2 into an unknown network, which shuts down/blocks the ssh into bash bunny. If anyone figures this out it would be much appreciated. Quote Link to comment Share on other sites More sharing options...
Dice Posted April 27, 2017 Share Posted April 27, 2017 What happens if you remove the bunny and the remove the drivers etc ? Start command prompt as administrator use the following command : set_devmgr_show_nonpresent_devices=1 then (in the same session) :start compmgmt.msc select devices and in the menu bar 'show hidden devices' use 'del' to remove all greyed out devices. --- set the bb to arming mode and plug it in. the 'new' ethernet controller should be recognised and get a new identifier. Set up the ics then Quote Link to comment Share on other sites More sharing options...
DavidDoherty Posted September 12, 2017 Share Posted September 12, 2017 Hi Dice. I followed this to the letter and there are now no greyed out devices. Unfortunately as soon as I select network sharing the bunny interface reverts back to unidentified network. While I can then connect via Putty I cannot ping anything and do not appear to have network connectivity. Any other suggestions on how to stop the interface reverting to "unknown" or why it does it? Cheers David Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.