Jay314
-
Posts
18 -
Joined
-
Last visited
Posts posted by Jay314
-
-
On 6/18/2017 at 11:44 PM, Fang_Shadow said:
Remember that linux uses both RNDIS_ETHERNET and ECM_ETHERNET, since it wants to be compatible with both windows and unix(mac). Has the usage of both storage and another attack mode work at the same time before on linux, or could be something different.
Are you saying I should set my payload with RNDIS and ECM attack modes?
-
On 6/19/2017 at 5:55 PM, Sebkinne said:
Yup, that's it. I have it working but it's a bit slow. There are some tricks to speed it up though, so once I finish that, I'll push out a new firmware.
That sounds great, since you seem pretty tied into the development, where would you recommend I look to find out more on the networking aspect of this project? There doesn't seem to be much documentation on the bash bunny.
-
On 6/20/2017 at 0:34 PM, Lord_KamOS said:
Did you get a shell?
I have no trouble accessing this system through serial, but networking still doesn't appear to be working properly.
-
46 minutes ago, Lord_KamOS said:
if that does not work, can you try it on a different computer?
Same results on a different machine (diff processors, diff Network Interface Card, diff mobo, same OS)
It starts a new interface but doesn't generate an IP
-
1
-
-
26 minutes ago, Lord_KamOS said:
if that does not work, can you try it on a different computer?
I just updated to version 1.3, but that didn't seem to make any difference, still not pulling an IP.
Just booted up my other linux system now, I'll let you know whether that solves the problem.
-
2 minutes ago, Lord_KamOS said:
if that does not work, can you try it on a different computer?
Sure
-
1
-
-
Just now, Lord_KamOS said:
Debian 8
Can you try re-flashing the firmware.
Sure, I'll let you know the results.
-
1
-
-
Just now, Dave-ee Jones said:
Yeah, so more than likely it's a driver issue...
Driver issue isn't likely, we're talking linux here, I'm on a debian system and the BB runs on debian also...
-
Just now, Lord_KamOS said:
Strange, i did the exact same thing and got a IP address.
Can I ask what Operating System you are using?
-
When mounting /dev/sdb (the BB) to /mnt/external/, the full path to the Payload is:
/mnt/external/payloads/switch1/payload.txt
The contents of the payload reads:
#!/bin/bash LED G ATTACKMODE STORAGE ECM_ETHERNETifconfig -a entry for the new interface reads:
eth1 Link encap:Ethernet HWaddr 00:11:22:33:44:55 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)-
1
-
-
8 minutes ago, b0N3z said:
switch your attackmode to STORAGE ECM_ETHERNET
I changed the payload to read:
ATTACKMODE STORAGE ECM_ETHERNET
There doesn't appear to be any change, and I am curious why the ordering would matter?
-
===========================SOLUTION==============================
Generate the following payload without STORAGE in the attackmode.
#!/bin/bash LED G ATTACKMODE ECM_ETHERNETThanks to Fang_Shadow, I've learned that using storage in concert ECM_ETHERNET prevents the system from pulling an IP (for what reason I still don't understand - I'm guessing it's just a bug).
I have had some issues with SSH but according to ifconfig (on local system) I see the interface is up and nmap scans show port 22 is open on the new IP, I'll update this post if anything changes.
===================================================================
Endgoal: I want to ssh from host machine into my BashBunny, then pivot from my BashBunny to a remote cloud hosted webserver, and write a testfile to that server.
Host System Used: Debian Linux
Crux: I am unable to acquire an ip address for my BashBunny using bb.shAttempts:
1. I tried to perform these actions from Arming Mode using the serial connection, however I learned that I am not able to share my network connection from serial mode and that Arming Mode only allows: Serial and Storage2. I attempted to run the default payload in order to gain network connectivity:
#!/bin/bash LED G ATTACKMODE ECM_ETHERNET STORAGEMy understanding of this code is that it will indicate it is ready when there is a solid green light (LED G) and that it will facilitate Ethernet connectivity and Storage (Last line), it is also my understanding that this initializes a new network interface that can be seen with the commands "ip addr" or "ifconfig -a".
However this new interface does not appear to be configured yet and attempting to run the command
ssh root@172.16.64.1does not result in the expected login prompt and eventually times out.
3. I've also attempted to run the bb.sh in order to share my hosts network connection, despite not being able to ssh into 172.16.64.1 IP. The script appears to work until you attempt to connect with it, and then it just hangs.
Any ideas on how to ssh into the BashBunny?
Thanks, Jay
-
1
-
(SOLVED) Cannot SSH into BashBunny from Debian/Linux Host
in Bash Bunny
Posted
Thank you @Fang_Shadow, this looks like it fixed the problem, albeit with slightly limited capabilities.
I now have an IP on my eth1 interface. Now I just need to configure the payload to throw me a shell, this has been a huge help!