How to Block SSL Pinning Bypass in Android Apps

Learn to Block SSL Pinning Bypass in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What is SSL Pinning?

Why Block SSL Pinning Bypass?

SSL Pinning Bypass tries to overcome SSL pinning by using dynamic instrumentation toolkits such as Frida. The bypass is based on a technique that replaces the certificate TrustManager used by the app, thus making the app trust any server certificate used by an attacker during an MitM attack. That allows the attacker to obtain sensitive information from requests coming from the app and at the same time manipulate the app by sending untruthful and malicious answers.

Prerequisites for Using Block SSL Pinning Bypass:

To use Appdome’s mobile app security build system to Block SSL Pinning Bypass , you’ll need:

• Appdome account (create a free Appdome account here)
• A license for Block SSL Pinning Bypass
• Mobile App (.apk or .aab for Android)
• Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)

Block SSL Pinning Bypass on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Block SSL Pinning Bypass without an SDK or gateway:

1. Upload the Mobile App to Appdome.

   1. Upload an app to Appdome’s Mobile App Security Build System

   2. Upload Method: Appdome Console or DEV-API
   3. Android Formats: .apk or .aab
   4. Block SSL Pinning Bypass Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps

2. Build the feature: Block SSL Pinning Bypass.

   1. Building Block SSL Pinning Bypass by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Block SSL Pinning Bypass feature as shown below:
      

      Figure 1: Fusion Set that will contain the Block SSL Pinning Bypass feature
      Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      2. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Block SSL Pinning Bypass feature via Appdome Console, to add the Block SSL Pinning Bypass feature to this Fusion Set.

      3. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below):

         Figure 2: Fusion Set Detail Summary
         Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      4. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Cirlce CI or other system:

         1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
         2. Look for sample APIs in Appdome’s GitHub Repository

   2. Building the Block SSL Pinning Bypass feature via Appdome Console

      To build the Block SSL Pinning Bypass protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.

         Like all other options in ONEShield™, Block SSL Pinning Bypass is turned on by default, as shown below:

         Figure 3: Block SSL Pinning Bypass option
         Note: The App Compromise Notification contains an easy to follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand specific support, workflow or other messaging.

      2. How: Toggle (turn ON) Block SSL Pinning Bypass, as shown below.

         Figure 3: Block SSL Pinning Bypass option

      3. When you select the Block SSL Pinning Bypass you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Block SSL Pinning Bypass

         

         Figure 4: Fusion Set that displays the newly added Block SSL Pinning Bypass protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).

   Congratulations!  The Block SSL Pinning Bypass protection is now added to the mobile app

3. Certify the Block SSL Pinning Bypass feature in Android Apps.

   After building Block SSL Pinning Bypass, Appdome generates a Certified Secure™ certificate to guarantee that the Block SSL Pinning Bypass protection has been added and is protecting the app. To verify that the Block SSL Pinning Bypass protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:

   Figure 5: Certified Secure™ certificate

   Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Block SSL Pinning Bypass has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block SSL Pinning Bypass and other mobile app security features are in each build of the mobile app