Android
founder:
depends on:
interested:	ruza biiter Yan
software license:
hardware license:

~~META: status = active ~~

People involved in this project are interested in better understanding of android platform, learning ways how to improve android security or customize android platform for their specific needs.

• Understand application compatibility mechanism in Android Market. How to fake compatibility, what it is based on.
• USB HID keyboard support, how to enable.
• Find really secure app lock application, try to circumvent its security mechanism, find application we can trust or research why it is not possible to trust any of currently aviable app locks.
• Do some radio research/review, post results on wiki.

• Various tools needed for disassembly/reassembly and basic diagnostic of android mobile / tablet (heatgun, various screwdrivers, osciloscope ..) in HW lab
• CM build enviroment ready for use (thx. 2 da3m0n22)
• bladeRF
• Android open acessory development kit

• GSM
• building from source
• security
• application creating & building
• reverse engineering
• rooting, sideloading

If you want to apply more deeply implemented features into android you need to implement them to the source code and then sucesfully build that code. If you need a feature which is implemented in another ROM in majority of cases the best solution is cherry-picking.

Many ROMs' source code is aviable on github .

A lot has been written about buidling roms, good starting point is to build AOSP or CM ROM from source (guide is on their webpages).

Before you install custom rom you need to unlock your device first. Fastboot. In case of Samsung you will need Heimdall which was written by “some guys from MIT.”

Here are located source-code editing guides/hints

• Editing settings apk on android 4.0+
• cargo cult cherry-pick of slimrecents
• debundling_cm_build

There is wiki entry related to specific rom & devices building, but tips and tricks could be applied globally.

• building CM on Grouper

Android have many security features. Some of them are implemented better, some of them not (f.e. ALSR ). Our goal in brmlab is to improve usage of those features. Security features implemented in Android are:

• iptables - implemented probably from version 1 till current, but without GUI. I use AFWall+ but maybe something better is out there.
• SELinux - permissive from 4.3, partial enforcement in 4.4, enforcing from 5.0
• ALSR - introduced in 4.0, PIE support from 4.1, non-PIE support dropped from 5.0
• application sandbox - sometimes could be escaped due to poorly written apps which store sensitive data in shared memory - check for example “android class hijacking” in exploit list below.
• Privacy Guard/App Ops - “Sandboxing customization.” Introduced in 4.3, not supported in new AOSP, CM supports some features but they dont care about privacy (permissions like “network acess” and similar is missing). MIUI Permission Manager looks very good, but guys from MIUI have some problems with understanding meaning of words “open source.” Maybe XPrivacy will do the trick. further research needed.
• Disc encryption - from 2.3.4

• Attack android OS through internet - Java exploits etc.
• Attacks through radio (baseband, modem) - even with very well implemented safety features on Android OS you need to “take care” of another processor, which is in every mobile phone.

RADIO (BASEBAND, MODEM) is another processor inside every mobile phone which is resposible for communication between BTS and your OS. It is closed source and not well documented playground (it is not easy to get nice and easily understandable articles related to this problematic). Source codes are from 80's and 90's with security mindset from that age.

• Samsung (unofficial) RADIO-WIRESHARK bridging: https://github.com/2b-as/xgoldmon
• Samsung “troubles” w radio: https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor
• Radio workaround (see part w HW selection), misc useful tips, interesting links inside: https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy

If you want to improve android security it's good to know the problem from another point of view, so you could easily adopt policy and changes to the code to prevent attack. It is obvious that nobody can predict how exactly 0day exploit looks like, but if you learn how to minimize impact even after sucesfull exploitation, you're one step further to save device.

• Cvedetails - filter on android http://www.cvedetails.com/product/19997/Google-Android.html
• Cvedetails - listed android vulns. https://www.cvedetails.com/vulnerability-list/vendor_id-1224/product_id-19997/Google-Android.html
• Exploit-db - filter on android vuln. https://www.exploit-db.com/platform/?p=android
• Adding exploit from exploit-db to metasploit http://www.kalitutorials.net/2014/06/add-new-exploits-to-metasploit-from.html
• Nexus security bulletins - list of android security issues with according CVE - monthly - https://source.android.com/security/bulletin/index.html
• Collection of tools - https://github.com/android-rooting-tools

Here are some of exploits known today to android platform, it serves mainly as link database to get some interesting info on special cases, old one is left in database for educational and historical meanings. For full coverage of known android vulnerabilities use cvedetails or exploit-db instead.

• CVE-2015-8505,8506,8507 http://www.cvedetails.com/cve/CVE-2015-8506/ interesting is that in https://source.android.com/security/bulletin/2015-12-01.html where should be reference to this CVE there is nothing about this CVE number, bulletin only covers CVE 6616.

• Libstagefright + ALSR bypass (useful for androids >5.1.1. and some 5.1.1.): stagefright + ALSR bypass report on exploit-db: here and here

• Android class loading hijacking - not exactly a bug, only weaknes which could be used in ODEX handling, usefull for badly writed apps on dalvik machine, androids >5.0 have dalvik, newer one runs or Art so for them its history: symatec official report (if you dont have javascript and similar crap everywhere read here)

• One Class to Rule Them All (useful for unpatched androids to some M preview, patched >4.4) - CVE-2015-3825: woot pdf report from usenix

• Browser Cross-Application Scripting (usfel for androids 2.3.4. and 3.1) - CVE-2011-2357: disclosure report from IBM

• GingerBreak (historical root, useful for androids 2.2-3.0): source from google code link to vuln database

• Exploid udev (historical root, useful for androids 1.x/2.x) : https://www.exploit-db.com/exploits/16099/

• RageAgainstTheCage (historical root, useful for androids 1.x/2.x) : https://github.com/georgiaw/Smartphone-Pentest-Framework/blob/master/exploits/Android/source/rageagainstthecage.c

• 7/2015 - Certifi-Gate report - how you can patch mRSTs to perform mRATs functionalities.
• 7/2012 - Android encryption Brute-Force - unlocked bootloader is needed, than via fastboot.
• 1/2011 - WebView Attacks - Attacks on Android web interaction component.

• https://www.owasp.org/index.php/Projects/OWASP_GoatDroid_Project
• http://thomascannon.net/blog/2010/11/android-data-stealing-vulnerability/
• http://www.privateerlabs.net/research/whitepapers/PRIVATEERLABS_MALICIOUS_INTENT.pdf?attredirects=0
• http://securitycompass.github.com/AndroidLabs/
• http://securitycompass.github.com/iPhoneLabs/
• http://blogs.iss.net/archive/Examining%20the%20recent.html
• https://www.trustwave.com/spiderlabs/advisories/TWSL2011-008.txt
• http://blog.spiderlabs.com/2011/09/google-android-focus-stealing-vulnerabiltiy-demo.html
• http://redmine.honeynet.org
• http://viaforensics.com/security/nopermission-android-app-remote-shell.html
• http://www.mcafee.com/us/downloads/free-tools/hacme-bank-android.aspx
• https://community.qualys.com/blogs/securitylabs/2012/07/25/android-security-evaluation-framework--a-s-e-f
• https://github.com/thomascannon/android-sms-spoof

• Android Development Series (thx. 2 da3m0n22)
• Introduction to Android development with Android Studio - Basic intro to Android Studio

• http://thomascannon.net/projects/android-reversing/
• http://www.woodmann.com/collaborative/tools/index.php/Category:Android_Tools
• http://forum.xda-developers.com/showthread.php?t=1910873
• http://code.google.com/p/android-apktool/
• http://wiki.base48.cz/AndroidRE

In many cases if you want to modify your device first you need to root it. There are many ready to use toolkits online but usually many of those have uknown source.

One solution to this problem is to compile your own root toolikt from open-source - f.e. Android run root shell (thx. 2 da3m0n22 for link)

From wiki: Replicant is a free and open source operating system based on the Android mobile platform, which aims to replace all proprietary Android components with their free software counterparts. This also makes it a security focused operating system as it closes discovered Android backdoors.

The problem is that it unfortunately cares only about radio implementation into android, but not radio itself.

Official project website

• http://blogs.nuxeo.com/dev/2011/10/speeding-up-the-android-emulator.html

• Bugtroid hacking tools collection
• Lucky patcher app manipulation on click
• ElectroDroid - Electronics work cheatsheet.
• Fing - Network Tools - Device discovery on wifi.
• AFWall+ - Front-end for iptables.
• ProxyDroid - Proxy for android. (better implementation)
• DocumentViewer - Document Viewer is a fork of the last GPL version of EBookDroid
• strongSwan - OpenSource IPsec-based VPN Solution

• http://code.google.com/p/androguard/
• Samsung Galaxy S3 tooolkit + Odin (formerly known as fastboot) (win)

• http://kitchen.yaam.mobi/
• http://lyt.no-ip.org/blog/Tag/dropad-a8/ (blog about Dropad A8 flashing, etc)
• http://rootzwiki.com/
• http://www.xda-developers.com/
• linx
• How WiFi works on Android

/dev/mtd/

• mtd0 handles miscellaneous tasks
• mtd1 holds a recovery image
• mtd2 contains boot partition
• mtd3 contains system files
• mtd4 holds cache
• mtd5 holds user data

• /system/media/bootanimation.zip /system/bin/bootanimation

./adb shell am start -a android.intent.action.MAIN -n com.android.email/.Settings

http://www.anddev.org/novice-tutorials-f8/using-the-am-tool-start-activities-intens-from-a-shell-t368.html

echo 00:50:`expr $RANDOM % 89 + 10`:`expr $RANDOM % 89 + 10`:`expr $RANDOM % 89 + 10`:`expr $RANDOM % 89 + 10`

CA certificate needs to be imported to verify server side of communication. Certificate can be in tis binary form with .pem filename suffix

Android Open Accessory Development Kit is available in brmlab

Hands-On with the Android Open Accessory Development Kit

29Btnas2He8

some hw mods documented on Picasa

Dropad A8 [NEKOMPLETNI]

• utv210_root.tgz. rozbalit na interni sd kartu.
• vypnout tablet
• vyndat externi sd kartu (ta co je ve slotu zvenku), jinak zustane flashovani viset na obrazku Tuxe
• stisknout Menu (M) a Power (C-)

http://www.youtube.com/user/MrTasselhof

http://www.slatedroid.com/topic/19289-guide-revive-your-dead-tablet/page__view__findpost__p__221288

1. Download HerotabC8_V2.2_2011_03_01.zip or Haipad_M7_0831_android2.3 Rooted.zip. (tested by ruza)
2. Take out the internal 4GB microSD and wipe it clean: dd if=/dev/zero of=/dev/sdX bs=512KB count=4 No need to do anything further, i.e. create partition or format.
3. Put the internal 4GB microSD back into the tablet.
4. Extract the contents of the ZIP. With u-boot-sd.bin from the ZIP, use dd to dump it onto an external microSD. I used a 2GB card for this. dd if=/path_to_bin/u-boot-sd.bin of=/dev/sdX
5. Copy the entire contents of the ZIP to the largest partition of the external microSD. It was the only automatically mounted partition when I replugged the card into Ubuntu.
6. I had to do these steps as recommended in the first post: rm -R utscript_sd && cp utscript utscript_sd (I didn't do it initially and after the recovery flash, my tablet couldn't boot w/o the external microSD)
7. Insert the external microSD into your tablet. Now, both microSDs are inside the tablet.
8. Press power and “M” button simultaneously. It should boot up and begin recovery. After that is done, you may remove your external microSD and proceed as your wish.

zdroj

• logcat show error mesage:

E/WifiHW  (  ): Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0":\\
No such file or directory will appear. 

• recreate /system/etc/wifi/wpa_supplicant.conf:

ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
update_config=1

more info about Android WPA supplicant

• porting to AOSP 6.0