Jump to content

Jay314

Active Members
  • Content Count

    18
  • Joined

  • Last visited

About Jay314

  • Rank
    Hak5 Fan

Profile Information

  • Gender
    Male
  • Interests
    DFIR, PurpleTeam, Ethical Hacking

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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!
  2. Are you saying I should set my payload with RNDIS and ECM attack modes?
  3. 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.
  4. I have no trouble accessing this system through serial, but networking still doesn't appear to be working properly.
  5. 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
  6. 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.
  7. Driver issue isn't likely, we're talking linux here, I'm on a debian system and the BB runs on debian also...
  8. Can I ask what Operating System you are using?
  9. @Lord_KamOS 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_ETHERNET ifconfig -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)
  10. 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?
  11. ===========================SOLUTION============================== Generate the following payload without STORAGE in the attackmode. #!/bin/bash LED G ATTACKMODE ECM_ETHERNET Thanks 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.sh Attempts: 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 Storage 2. I attempted to run the default payload in order to gain network connectivity: #!/bin/bash LED G ATTACKMODE ECM_ETHERNET STORAGE My 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.1 does 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
  12. I just attempted to run the bb.sh config again, while loading the attack payload, and it's still hanging.
  13. I should also mention that while I don't get a new IP, i do get a new network interface: eth1, but it doesn't appear to be configured.
×
×
  • Create New...