How to intercept all Android HTTP / HTTPS network traffic on Windows and bypass SSL Pinning
- Install ADB / Android SDK or use the AppUse VM
- Root the android device
- Install Android Cydia Substrate
adb install com.saurik.substrate.apk
- Install Android SSL Trust Killer
adb install Android-SSL-TrustKiller.apk
- Export Burp Root CA Certificate
- Push Burp Cert to the sdcard
adb push PortSwiggerCA.cer /sdcard
- Install Burp Cert in the Android Trust Store
Settings > Security > Install from device storage
- On Windows, create a Wireless hotspot sharing your Internet / external connection
- Create the hotspot:
netsh wlan set hostednetwork mode=allow ssid=MyHotspot key=MyPassword keyUsage=persistent
- To start the hotspot
netsh wlan start hostednetwork
- Or to stop the hotspot:
netsh wlan stop hostednetwork
- Enabled Internet Connection Sharing with your external connection:
Right click your connection's NIC, "Sharing" tab, check the box, select "MyHotspot". The external NIC icon should say "shared".
- Connect the Android to the wifi Hotspot using the key configured previously.
- Optional: If you prefer to use a static network configuration as opposed to DHCP, go to the Wifi connection advanced settings and look for the IP address attributed. Switch to a static IP and set this IP manually. The gateway should be the IP address of the Windows "MyHotspot" interface. The DNS Server should be your ISP's / corporate network one. Reconnect the Wifi with the new network configuration.
- Try to ping the Android device's IP address from the Windows.
- Run Burp and make it listen on the Hotspot's interface IP address.
- You can configure this proxy in the Wireless connection advanced settings, but that would take effect only for proxy-aware apps such as the web browser. Preferably, and since your device is rooted, use an app such as ProxyDroid to make all the apps go through the proxy transparently. You should have Play Store working as well.
- Configure your Burp's upstream proxies rules if needed.
- You should be able to intercept all HTTP/HTTPS traffic. If not, well, go back to step 1.
No comments:
Post a Comment