HTTP(S) Proxy for Android
Intercept traffic going from and to an emulated Android device with Burp Suite
When you have an Android emulator set up in Android Studio, you can change some settings to be able to intercept traffic in a Proxy like Burp Suite. This can be really useful when you want to view or test web functionality that an app uses, as this might reveal interesting vulnerabilities because developers might not expect the app to be reverse-engineered in this way.
One tool we'll use throughout this process is ADB. Make sure you're inside Android Studio to be able to use it, or find its absolute path.
Configure the Proxy
Every time you start your device and want to intercept its traffic, you should set up the proxy configuration so that all traffic gets sent through your Burp Suite instance.
Below are 2 methods of doing this, either through the CLI (easiest) or through the GUI.
ADB
To make connecting to your local IP easy, we will set up a reverse port forward from the device's 8080 to your 8080. This way, we can target 127.0.0.1 on the device in the future, and this will send it over to your host system for Burp Suite to intercept.
adb reverse tcp:8080 tcp:8080Next, The following two commands configure the device to send all traffic through this port.
adb shell settings put global http_proxy 127.0.0.1:8080
adb shell settings put global https_proxy 127.0.0.1:8080Of course, you should have Burp Suite running on your host system at this point and can see HTTP requests coming in, although HTTPS websites will likely still cause certificate errors. See Install Certificate Authority (HTTPS) for a guide on how to fix this.
GUI
In case you want to rather configure the proxy via the GUI, you can use the emulator's display to do so. First start your device with the following command (use emulator -list-avds to get the names):
emulator -avd Pixel_6_Pro_API_34On the right you should see a bar of options and 
three dots for more options. Click it and visit Settings -> Proxy. Here you can set a Manual proxy configuration to the IP address and port of your proxy. You will likely need to configure an external address because localhost points to the device itself, not your host.
You can now easily test if it works by opening the Chrome app and visiting http(s) websites like http://example.com/ and https://example.com/.
Tip: If your Burp Suite proxy is not on localhost (127.0.0.1), you will need to set a different Host name and also edit the Proxy Listener from its Options menu. For Bind to address choose All interfaces to allow connections from anywhere. In this case, also make sure that your firewall is not blocking the listening port.
Install Certificate Authority (HTTPS)
To get rid of certificate errors caused by Burp Suite intercepting HTTPS requests, you must tell the Android device to trust its custom certificate authority.
This describes 2 methods which should both work, but one may be easier than the other depending on your setup. If possible, start with the manual approach because it should work on all types of devices.
Manual via Settings
With the Configure the Proxy steps taken, you should be able to visit http://burp on your device and end up on Burp Suite's configuration page.
Click the CA Certificate button on the top right and download it to some location on the device. Then, go into your settings and look for "Certificate", you should find some option to install a CA certificate as in the screenshot below.
On this Android version, you have to press Install Anyway to start selecting a certificate file from your Downloads. Choose the cacert.der file from Burp Suite.
If everything went successfully, you should receive a small message saying "CA certificate installed".
You can now visit HTTPS websites in your browser, and then should be visible in Burp Suite without any certificate errors. Some apps however will still be able to detect the tampering with certificates and possibly not allow you to use them, this is where HTTP(S) Proxy for Android comes in.
CLI via ADB
You should first download the certificate from Burp Suite via its GUI. Go to Proxy -> Options, then click the Import/export CA certificate button, and choose for exporting a Certificate in DER format. You should save it with the name: cacert.der.
Next, we need to convert it to the PEM format that Android expects:
We need to also give it a correct name consisting of the "issuer hash", which can be found like this:
Your hash may be different, but you simply have to append .0 to it to get your final filename:
This part was tested in API version <= 28 (Android 10) to avoid issues with permissions on the /system folder. Your success may vary.
We need to move the certificate from our host to the Android device. To do this, we need to set a -writable-system flag on the device with the emulator tool. Check out ADB for more information about how to access this binary.
Next we need to mount the directory as writable so that we can copy files into it:
Finally, push the file into /system/etc/security/cacerts and give it the correct permissions (664):
Then reboot the device to apply the changes (permanently):
To verify if this worked, you can start the device again in Android Studio and look at Settings -> Security -> Trusted Credentials which should show "PortSwigger" now:
Last updated