Sinisterly
is there a working payload for android 4.x devices in msf?? - Printable Version

+- Sinisterly (https://sinister.ly)
+-- Forum: Hacking (https://sinister.ly/Forum-Hacking)
+--- Forum: Network Hacking (https://sinister.ly/Forum-Network-Hacking)
+--- Thread: is there a working payload for android 4.x devices in msf?? (/Thread-is-there-a-working-payload-for-android-4-x-devices-in-msf)



is there a working payload for android 4.x devices in msf?? - Num5kull - 10-23-2017

Trying to get a reverse connection using msf venom on android 4.x.
The apk i have generated crashes after sending initial connection to the listener.
any ideas?


RE: is there a working payload for android 4.x devices in msf?? - phyrrus9 - 10-23-2017

(10-23-2017, 03:27 PM)Num5kull Wrote: Trying to get a reverse connection using msf venom on android 4.x.
The apk i have generated crashes after sending initial connection to the listener.
any ideas?

If you have adb, you can try attaching a usb debug session to get a stack trace. You might also find that in the syslog.
If you can provide a stack trace and the source code I can help you figure out what's going on.

Usuallly with network application crashes, they're in socket code that doesn't have proper error handling. My guess is you're writing data to a socket that's not open (tcp), or you don't have permission to send data (udp)


RE: is there a working payload for android 4.x devices in msf?? - Num5kull - 10-24-2017

Ill check it out soon and give a log cat dump. All the android exploits are for android 5+ so the payload os prob for android 5+ aswell, l8rz Smile


RE: is there a working payload for android 4.x devices in msf?? - Num5kull - 12-09-2017

Just got back to this, setup a logcat dump on the device and a machine to connect back to....

it turned out i forgot to set the payload on the listener; so was getting android app error out.

After adding set payload android/meterpreter/reverse_tcp to my method the reverse connection worked perfectly.

Hope this helps Biggrin
N