Cybersecurity

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== BBC Ch 23: Android Hacking ======

//Source: Bug Bounty Bootcamp by Vickie Li//

Android apps communicate with the same backend APIs as web apps. Many web vulnerabilities (IDORs, SQLi, XSS, auth bugs) appear in the mobile surface. Android-specific issues include certificate pinning bypass, hardcoded secrets in APKs, and insecure local storage.

===== Setting Up a Mobile Proxy =====

Route Android traffic through Burp Suite to intercept HTTPS:

  - Configure Burp listener on 0.0.0.0:8080
  - On the device: Settings -> Wi-Fi -> proxy -> manual -> enter Burp machine IP:8080
  - Install Burp CA cert on the device (download from http://burp via the device browser)
  - For Android 7+: user-installed CAs are not trusted by apps; use a rooted device or emulator

===== Bypassing Certificate Pinning =====

Apps with certificate pinning reject Burp's CA. Bypass options:

**Frida (dynamic instrumentation):**
<code>
frida-server  # running on device
frida -U -f com.target.app -l ssl_bypass.js --no-pause
</code>

**Objection (Frida-based, simpler interface):**
<code>
objection -g com.target.app explore
android sslpinning disable
</code>

After disabling pinning, Burp intercepts all HTTPS traffic from the app.

===== APK Anatomy =====

An APK is a ZIP file. Key contents:
  * ''AndroidManifest.xml'' -- permissions, exported activities/receivers/providers, intent filters
  * ''classes.dex'' -- compiled Dalvik bytecode
  * ''res/'' -- resources including ''strings.xml'' (often contains hardcoded secrets)
  * ''assets/'' -- bundled files, sometimes including config and certificates
  * ''lib/'' -- native .so libraries

===== Toolchain =====

**ADB (Android Debug Bridge):**
<code>
adb devices                         # list connected devices/emulators
adb install target.apk              # install APK
adb pull /data/data/com.target.app/ # pull app data directory (requires root)
adb push file.txt /sdcard/          # push file to device
adb shell                           # interactive shell on device
</code>

**Apktool (decompile/recompile APK):**
<code>
apktool d target.apk -o output/    # decompile to Smali + resources
apktool b output/ -o repackaged.apk  # rebuild
</code>

**Frida (dynamic instrumentation):**
Hook Java methods at runtime, bypass cert pinning, trace function calls.

**MobSF (Mobile Security Framework):**
Automated static + dynamic analysis. Upload APK to get a full vulnerability report: exported components, hardcoded secrets, insecure API usage, permissions audit.

===== Hunting for Vulnerabilities =====

==== Static Analysis ====

Decompile the APK with Apktool or jadx, then:
<code>
grep -r "password\|secret\|api_key\|token\|AWS\|Bearer" output/
grep -r "http://" output/           # cleartext HTTP endpoints
cat output/res/values/strings.xml   # hardcoded strings
cat output/AndroidManifest.xml      # exported components
</code>

Exported activities, content providers, and broadcast receivers can be triggered by other apps or adb:
<code>
adb shell am start -n com.target.app/.AdminActivity
adb shell content query --uri content://com.target.app/users
</code>

==== Dynamic Analysis ====

  * Route traffic through Burp; replay and manipulate API requests
  * Look for the same bugs as web: IDORs (change user_id), broken auth, SQLi in search fields, XSS in WebViews
  * Check local storage for sensitive data:
<code>
adb shell
run-as com.target.app
ls databases/
cat databases/app.db | strings
cat shared_prefs/*.xml
</code>

==== SQLite Databases ====

Apps often store data in unencrypted SQLite files:
<code>
adb pull /data/data/com.target.app/databases/app.db
sqlite3 app.db
.tables
SELECT * FROM users;
</code>

===== 5-Step Checklist =====

  - Set up Burp proxy; bypass cert pinning with Objection (android sslpinning disable) to intercept HTTPS.
  - Decompile APK with Apktool or jadx; grep strings.xml and source for hardcoded credentials, API keys, and HTTP endpoints.
  - Check AndroidManifest.xml for exported components accessible without permission; trigger them via adb.
  - Pull local databases and shared preferences; check for sensitive unencrypted data.
  - Replay and manipulate intercepted API requests looking for IDORs, broken auth, SQLi, and XSS -- same methodology as web.