Skip to main content

How to use MobSF with Genymotion Device image (PaaS) for Cloud providers?

  • Updated

In this tutorial, it is assumed that you are familiar with MobSF and you are using it from a physical local machine. For detailed information about MobSF, please refer to MobSF documentation.

Prerequisite

Setup your Genymotion instance

1. Quickstart

Before proceeding, please read Genymotion Device image (PaaS) Requirements carefully.

Then, refer to Genymotion Device image Quickstart to get started with Genymotion for your Cloud provider (AWS, GCP, Alibaba, MS Azure, Oracle Cloud).

2. Network

Your instance must have a Public IP or it will not be reachable from your local machine. This IP will change every time the instance is shutdown and booted.

If you wish to keep the same Public IP, we recommend using a persistent public IP, such as Elastic IP if you are using AWS.

3. Security/Firewall

MobSF uses adb to communicate with Genymotion instance via TCP port 5555.

So, add an inbound rule to your EC2 firewall/security to open TCP port 5555 for your local machine IP only:

AWS_firewall.png

Danger

Do not allow TCP port 5555 to anyone (0.0.0.0/0). ADB connection is not secure - opening TCP port 5555 to anyone may compromize your instance security! Only allow your local machine IP.

4. Enable ADB

You need to enable ADB on your Genymotion instance. To do so:

  1. Access your Genymotion instance display
  2. Go to Configuration and Enable ADB
    AWS_adb.png

For more details and alternate methods, please refer to How to enable ADB?

Setup MobSF

From your local machine, ensure that you can connect to your Genymotion instance via adb:

adb connect <public_ip>:5555
adb devices

For example:

$ adb connect 54.78.205.214:5555
connected to 54.78.205.214:5555
$ adb devices
List of devices attached
54.78.205.214:5555 device

You can now perform MobSF Dynamic Analysis with your Genymotion instance.

If Dynamic Analyzer doesn't detect the instance, you need to manually configure ANALYZER_IDENTIFIER in <user_home_dir>/.MobSF/config.py, or via environment variable ANALYZER_IDENTIFIER, with the instance public IP.

For example: ANALYZER_IDENTIFIER = '54.78.205.214:5555'.

If MobSF cannot detect adb, you need to configure ADB_BINARY in <user_home_dir>/.MobSF/config.py.

For example: ADB_BINARY = '/Applications/Genymotion.app/Contents/MacOS/tools/adb'.

Related articles