When testing Android apps, one often wants to gain visibility into HTTP requests that the app makes in order to test the back-end services for security vulnerabilities. These days, this traffic is TLS encrypted. To enable yourself as a man-in-the-middle for your own device, you can install custom certificate authorities (CAs) and configure the device to use an HTTP proxy just as you would a browser.
However, Android distinguishes between certificates installed by the user and certificates that came with the operating system. Apps can choose to trust only the system certificates, and apps that target API level 24 and higher do this by default. This article describes how to modify an app to make it trust user CA certificates.
This article assumes:
- You have the TLS intercept proxy of your choice up and running (such as Burp Suite).
- Your Android device has the CA certificate that the proxy is using installed on the device as a user CA (search settings for Certificates).
- Your Android device is using the proxy (configured in the advanced settings for your WiFi connection), and the proxy can see TLS traffic through apps that will trust your CA by default (such as Chrome).
- The app you’re working with is not doing certificate pinning in code.
Extract the Original App Package
Extract the original app APK file using apktool:
This command will unpack the APK file into the
app subdirectory where you’ll find decompiled code and various resources for the app.
Next, we’ll modify
AndroidManifest.xml to load a custom XML configuration snippet that will enable trust for user CAs in the app. Add an
android:networkSecurityConfig="@xml/network_security_config" attribute to the
<application> tag. Here’s an example abbreviated
This will cause Android to include the XML configuration snippet at
app/res/xml/network_security_config.xml. Next we’ll place the relevant configuration there. Create the
app/res/xml directory if it doesn’t exist. Here’s the entirety of
This configuration will make the app trust user-installed CAs during TLS connections.
If you’d like to make any other modifications to the app, now is the perfect opportunity. We’ll be repackaging the app next.
Repackaging the APK
Build a new APK file incorporating your changes. Again, assuming the app code modified above is in the
The APK file needs to be signed, but any signature will work. This guide will generate a new key and certificate for this purpose.
Generate a 1024 bit RSA keypair and store it in the key file using openssl:
Next, convert the key to PKCS#8 as required by APK. The key in PKCS#8 format will be placed in
Now generate a certificate, sign it with our key, and store it in
Next, zipalign the APK (
zipalign is a part of Android Studio and can be found at
~/Android/Sdk/build-tools/<version> with Android Studio is installed):
Finally, sign the APK file with apksigner using the key and certificate we generated above. apksigner is part of Android Studio and can be found at
~/Android/Sdk/build-tools/ with Android Studio installed.
app-modified-signed.apk is the app with your modifications ready for installation. Copy it to your device and install it. If it is your first time, you may need to grant app install permissions to your file manager app (or whatever app you’re initiating the installation from). If you were successful, you should now see HTTPS traffic requested by the app in your proxy.
Android apksigner Reference
Changes to Trusted CAs
Manifest Security Config Reference