Jump to content

[RELEASE] Bash Bunny 1.1


Recommended Posts

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Introducing Bash Bunny firmware v1.1 A feature packed firmware awaits Bash Bunny users just one month after release. We've excited to announce version 1.1, including many new features, conveniences,

First! :)

Yeah, it's possible old payloads do not work in regards to LED codes, and bunny_helpers.sh is now outdated. We will be pushing changes to the github payloads repository today. This is correct

22 hours ago, peterkozmd said:

okay looks like it installed, but not certain how to verify? also how to make certain helpers are installed as well.

Check the version.txt in both the root and the /udisk folder.

 

Also : 

 

On the bunnyheader it states : 

SMP PREEMPT Thu Apr 6 00:46:27 PDT 2017 armv7l

 

Would be a nice to have to get the serial included in here

Link to post
Share on other sites

the version file states 1.1_128 but that could just mean the txt copied over. also not seeing a udisk folder.Looks like the new folder structure came over but still not convinced it went through the firmware update  properly, Where do i see the bunny header?

 

again sorry for the inconvenience and thanks for the help

Link to post
Share on other sites

Look up the com port the BB is using and connect to it using the Directions Darren gave using Putty

Start compmgmt.msc and see which prt has been used

 

Start putty

Select Serial connection on the com port you got previously

Set speed to 115200 Baud

Connect and log on as root with the default password

See the ascii art header and the date. :P

 

 

 

Edited by Dice
Link to post
Share on other sites
6 minutes ago, peterkozmd said:

Thank you. Yeah it shows that header when i putty into it. just was not sure because i don't recall it going through the red/blue flashing sequence.

Maybe someone with indepth knowledge is able to give a more definitive answer than a text file..

 

Maybe a command that shows the core-version etc?

Link to post
Share on other sites
On 7/4/2017 at 3:57 AM, illwill said:

@hardrock78 try something like this if you are testing on windows


LED B SLOW

ATTACKMODE RNDIS_ETHERNET
LED STAGE1
GET TARGET_IP;GET TARGET_HOSTNAME;GET HOST_IP

ATTACKMODE HID
LED STAGE2
RUN WIN NOTEPAD
Q DELAY 1000
Q STRING Switch#:${SWITCH_POSITION} - IP:${TARGET_IP} - HOST:${TARGET_HOSTNAME} - BunnyIP: ${HOST_IP}

LED FINISH

 

I did try this code and my return is:

 

Switch£çswitch2 ' IPç ' HOSTç ' BunnyIPç 172.16.64.1

does that mean anything is not working ? looks like the only variables returned are switch&host_ip but not target_ip & hostname ?

no clue but probably is related to the quickcreds not working ..

Link to post
Share on other sites
On 4/14/2017 at 1:11 PM, johnjohnsp1 said:

I did try this code and my return is:

 

Switch£çswitch2 ' IPç ' HOSTç ' BunnyIPç 172.16.64.1

does that mean anything is not working ? looks like the only variables returned are switch&host_ip but not target_ip & hostname ?

no clue but probably is related to the quickcreds not working ..

You need to specify which keyboard layout you have if you don't have US keyboard. To do this, make sure all the languages files are in the language folder on the bunny and Put this after ATTACKMODE HID 

DUCKY_LANG us 

Replace us to which language you want. Then it should work fine.

Link to post
Share on other sites
9 hours ago, zobie said:

Was the update intentionally removed? I'm getting a Connection error when trying to download.


https://storage.googleapis.com/bashbunny_updates/ch_fw_1.1_228.tar.gz

 

Nope, it's still there and works for me. I tested using a few different connections too. 

Link to post
Share on other sites

Total newb here but I flashed my BB with the new firmware and everything seemed to go okay and when I opened BB in file explorer everything seemed to be in order so I copied over impacket and responder into tools.  However, when I got into the serial interface I see this.

root@bunny:~# ls
udisk  version.txt
root@bunny:~#
root@bunny:~#
root@bunny:~#
root@bunny:~# ls udisk
root@bunny:~#
 

 

can anyone tell me what I'm doing wrong.

Link to post
Share on other sites

Udisk isn't mounted when storage is used as an attack mode, if it was HID or Ethernet it would from what I've seen. To mount Udisk type the following:

mount -o sync /dev/nandf /root/udisk

 

Then you should see what is in your udisk. Your tools installed should be under /tools/ not under /root/udisk/

Link to post
Share on other sites

Hello,

I'm unable to find the responder, which I know is required to perform QuickCreds. I even downloaded bashbunny-payloads-master but even then I couldn't find the tools_installer folder. Does anyone know where I can find the responder and how to transfer it to the correct folder, to perform QuickCreds?

Link to post
Share on other sites

My firmware update went pretty smooth.. 

Just copied the download, checked the hash, moved it to the main dir in arming mode, removed, plugged back in - LED sequence was as expected.


Only thing I noticed so far was mixing LEDs like (LED R B) doesn't work anymore. Not a big deal for me - maybe there's a new way to do it I haven't looked up yet. 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.


×
×
  • Create New...