|
37 | 37 | - [ ] Is there any [password hard coded or saved in disk](android-app-pentesting/index.html#poorkeymanagementprocesses)? Is the app [using insecurely crypto algorithms](android-app-pentesting/index.html#useofinsecureandordeprecatedalgorithms)?
|
38 | 38 | - [ ] All the libraries compiled using the PIE flag?
|
39 | 39 | - [ ] Don't forget that there is a bunch of[ static Android Analyzers](android-app-pentesting/index.html#automatic-analysis) that can help you a lot during this phase.
|
| 40 | +- [ ] `android:exported` **mandatory on Android 12+** – misconfigured exported components can lead to external intent invocation. |
| 41 | +- [ ] Review **Network Security Config** (`networkSecurityConfig` XML) for `cleartextTrafficPermitted="true"` or domain-specific overrides. |
| 42 | +- [ ] Look for calls to **Play Integrity / SafetyNet / DeviceCheck** – determine whether custom attestation can be hooked/bypassed. |
| 43 | +- [ ] Inspect **App Links / Deep Links** (`android:autoVerify`) for intent-redirection or open-redirect issues. |
| 44 | +- [ ] Identify usage of **WebView.addJavascriptInterface** or `loadData*()` that may lead to RCE / XSS inside the app. |
| 45 | +- [ ] Analyse cross-platform bundles (Flutter `libapp.so`, React-Native JS bundles, Capacitor/Ionic assets). Dedicated tooling: |
| 46 | + - `flutter-packer`, `fluttersign`, `rn-differ` |
| 47 | +- [ ] Scan third-party native libraries for known CVEs (e.g., **libwebp CVE-2023-4863**, **libpng**, etc.). |
| 48 | +- [ ] Evaluate **SEMgrep Mobile rules**, **Pithus** and the latest **MobSF ≥ 3.9** AI-assisted scan results for additional findings. |
40 | 49 |
|
41 | 50 | ### [Dynamic Analysis](android-app-pentesting/index.html#dynamic-analysis)
|
42 | 51 |
|
|
52 | 61 | - [ ] This one is really important, because if you can capture the HTTP traffic you can search for common Web vulnerabilities (Hacktricks has a lot of information about Web vulns).
|
53 | 62 | - [ ] Check for possible [Android Client Side Injections](android-app-pentesting/index.html#android-client-side-injections-and-others) (probably some static code analysis will help here)
|
54 | 63 | - [ ] [Frida](android-app-pentesting/index.html#frida): Just Frida, use it to obtain interesting dynamic data from the application (maybe some passwords...)
|
| 64 | +- [ ] Test for **Tapjacking / Animation-driven attacks (TapTrap 2025)** even on Android 15+ (no overlay permission required). |
| 65 | +- [ ] Attempt **overlay / SYSTEM_ALERT_WINDOW clickjacking** and **Accessibility Service abuse** for privilege escalation. |
| 66 | +- [ ] Check if `adb backup` / `bmgr backupnow` can still dump app data (apps that forgot to disable `allowBackup`). |
| 67 | +- [ ] Probe for **Binder-level LPEs** (e.g., **CVE-2023-20963, CVE-2023-20928**); use kernel fuzzers or PoCs if permitted. |
| 68 | +- [ ] If Play Integrity / SafetyNet is enforced, try runtime hooks (`Frida Gadget`, `MagiskIntegrityFix`, `Integrity-faker`) or network-level replay. |
| 69 | +- [ ] Instrument with modern tooling: |
| 70 | + - **Objection > 2.0**, **Frida 17+**, **NowSecure-Tracer (2024)** |
| 71 | + - Dynamic system-wide tracing with `perfetto` / `simpleperf`. |
55 | 72 |
|
56 | 73 | ### Some obfuscation/Deobfuscation information
|
57 | 74 |
|
58 | 75 | - [ ] [Read here](android-app-pentesting/index.html#obfuscating-deobfuscating-code)
|
59 | 76 |
|
60 | 77 |
|
61 | 78 | {{#include ../banners/hacktricks-training.md}}
|
62 |
| - |
63 |
| - |
64 |
| - |
|
0 commit comments