Android hacking and security, part 1: Exploiting and securing application components
Mobile Application Security is one of the hottest segments in the security world, as security is really a big concern with growing mobile applications.
In this article, we will go through the attacks associated with Android application components.
What are android application components?
Application components are essential building blocks of an Android App. Every app is built as a combination of some or all of those components, which can be invoked individually. There are four main components in Android, which are explained below.
Activity: An Activity provides a screen with which users can interact in order to do something. Users can perform operations such as making a call, sending an SMS, etc.
Example: Login screen of your Facebook app.
Service: A Service can perform long-running operations in the background and does not provide a user interface.
Example: Playing Music
Content Providers: A content provider presents data to external applications as one or more tables. In other words, content providers can be treated as interfaces that connect data in one process with code running in another process.
Example: Using content providers, any app can read SMS from inbuilt SMS app’s repository in our device.
*READ_SMS permission must be declared in the app’s AndroidManifest.xml file in order to access SMS app’s data.
Broadcast Receivers: A broadcast receiver is a component that responds to system-wide broadcast announcements such as Battery Low, boot completed, headset plug etc. Though most of the broadcast receivers are originated by the system, applications can also announce broadcasts.
This article focuses on demonstrating the methodology to attack and secure vulnerable Activity components of applications.
You can download the sample application used in this article and follow the steps along with us.
Fill out the form below to download the APK file and Source Code.
As shown in the figure below, this app has two activities. The first activity takes a password as input. If the user enters the correct password he will be landed in a page which says “Private Area”, otherwise he will get a “Wrong password” message. For test purposes, the password to login is set as “password”. Ideally, the first screen should use an intent and invoke the second screen if a valid password is entered. We need to perform black box testing on this app to see if we can bypass the authentication by directly invoking the welcome screen.
Prerequisites to follow the steps
Computer with Android SDK Installed
A Non Rooted mobile device to install the app.
Attacking Vulnerable Activity Components
Securing the applications
- Decompile the app with APK tool.
- Analyze AndroidManifest.xml file for exported Activity components.
Every Android App has a package name and every Activity has its own Class name inside the package. The initial steps are to find out the name of the package and names of the available sensitive activities. Though there are other methods to get this information, looking at the AndroidManifest.xml is a good approach. We can get the AndroidManifest.xml file by decompiling the application using APKTOOL.
- Download APKTOOL from the link: https://code.google.com/p/android-apktool/downloads/list
- Place the test application in the same folder as in APKTOOL.
- Now, decompile the APK file using the following command as shown in the figure:
apktool d testapp.apk
As shown in the figure below, we should now be able to see a new folder named “testapp” with the AndroidManifest.xml file inside it.
Now, we need to search for the package name and its activities.
All the activities will be registered in AndroidManifest.xml file using <activity></activity> tags. So, anything inside these tags will be an activity. Looking at the AndroidManifest.xml file, we are able to see two Activity Components and the package name as shown in the figure below.
By examining the above figure, it is clear that we got the following information about the app.
com.isi.testapp is the name of the package.
com.isi.testapp.Welcome could be the activity we are getting after providing the correct password.
Attacking vulnerable activity components
Our job now is to launch Welcome activity without providing any password in the first screen.
We can perform attacks on vulnerable activity components in several ways, as mentioned below.
- Launching sensitive Activities with Activity Manager Tool.
- Using a Malicious App to invoke Activities of other apps.
- We can also use Mercury framework for performing these attacks, which will be covered in later articles.
Launching sensitive activities with Activity manager tool
Activity Manager is a tool that comes preinstalled with Android SDK and can be used along with “adb shell”. This tool can be used to launch Activities and Services of an application. We can even pass intents using it.
So, let’s begin.
- Connect the device to the computer and get a shell on the device using the following command:
- Type in the following command to launch the Welcome activity:
am start –n com.isi.testapp/.Welcome
We should now see the welcome screen fired up without providing the password.
Using a Malicious App to invoke Activities of other apps
Another way of invoking other application’s activities is to write a malicious app and feed it with the name of the package and activity to be launched. The figure below is a code snippet to launch an activity where in com.isi.testapp.Welcome is the activity to be launched. In our case, the malicious app doesn’t require any permission to launch the “Welcome” activity of the vulnerable app.
Using Mercury framework
The same attack can be reproduced with Mercury framework. We will discuss Mercury framework later in this series.
Securing the application components
- Setting android:exported attribute’s value to false
In the AndroidManifest.xml file of our application, we should add the following attribute to the application component to be secured. In our case com.isi.testapp.Welcome
is the activity to be secured.
The above code restricts other applications or any system component other than the current app from accessing this Activity. Only applications that have the same user id as the current app will be able to access this Activity.
- Limiting access with custom permissions
The android:exported attribute is not the only way to limit an activity’s exposure to other applications. We can also impose permission-based restrictions by defining custom permissions for an activity. This is helpful if the developer wants to limit the access to his app’s components to those apps which have permissions.
Note: The above security controls are applicable to any other Application component which we discussed in the beginning of the article.