Skip to main content

Andorid Security Assessment

Recently I got a chance to do security assessment of an Android-based app. As the Internet is full of the methods of doing Android assessment, here I shall try to list down major steps to perform it.
For Intercepting traffic:
1. Download the Android SDK tool from http://developer.android.com/sdk/index.html. It includes SDK and AVD (Android Virtual Device). They are necessary for creating the VM and installing emulator.
2. Once, emulator started, install the android app's .apk file on it. 
3. Configure local web proxies, eg Burp, Paros to intercept the traffic by modifying the Internet setting in Android by Settings->Wirless & Network Settings-> Mobile Networks -> Access Point Names-> Proxy Name(PC's IP address) & Port.
4. Now we may perform the assessment as we do for normal web application.

Code review of the app:
1. Rename the .apk file to .zip file and extract it. You'll find classes.dex file which can be converted into a jar file using a tool called dex2jar. 
2 Now use JD-GUI to convert the jar file to Java source code. Now source code is human readable and a code review can be done on it.

Reviewing the AndroidManifest file for permissions:
1. The AndroidManifest.xml resides into the same folder where classes.dex is available.
2. You need to convert the xml file into a readable text file using a tool called AXMLPrinter2.jar. Go to http://developer.android.com/guide/topics/manifest/manifest-intro.html for info on reviewing permissions contained in AndroidManifest.xml file.

Android app sign check:
1. To check if the application is signed or not you may use a java tool, found in the bin directory of Java installation, called jarsigner:
$ jarsigner -verify my_signed.apk
If the .apk is signed properly, Jarsigner prints "jar verified"
2. To see the certificate information, run the following tool found in the same bin directory:
keytool -printcert -file VScert.cer >> CertDetails.txt

There might be other aspects of Android App assessment as well, that may vary depending on the application,  but these are the few major and necessary methods.

Comments

Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more