Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Droidcon IT 2014

Marco Grassi
February 06, 2014

Droidcon IT 2014

Marco Grassi

February 06, 2014

More Decks by Marco Grassi

Other Decks in Research



    Torino 2014 ! Marco Grassi @marcograss - Mobile Security Analyst @ viaForensics
  2. $ whoami • R&D Team Member @ viaForensics • Developer

    background (both Android and iOS) • Part of my job is to attack and break mobile apps
  3. AGENDA • Reverse Engineering and Obfuscation • Tampering Detection •

    Logging • File Storage • Secure Network Communications • IPC Attack Surface • RAM memory attacks • More Advanced Material : Runtime Manipulation • Extra: Creating Cheats for Android Games : )
  4. REVERSE ENGINEERING FREE TOOLS • apktool and smali/baksmali It will

    provide us a disassembled representation of the Dalvik bytecode, so sort “low level”, with registers, but very understandable because of bytecode metadata. Very useful to disable tampering protections, the code can be modified and the application can be recompiled and resigned.
  5. REVERSE ENGINEERING FREE TOOLS • dex2jar + Java decompiler (jd-gui,

    jad …) dex2jar will convert the .dex file to a .jar containing Java code We can then use the freely available Java decompilers and obtain back a Java representation of the code. Very readable if no obfuscation is in place.
  6. REVERSE ENGINEERING PRO TOOLS • JEB Decompiler Renaming feature, very

    handy with obfuscated applications Python APIs Native Dalvik decompiler, it does not pass through Java byte code, decompilation is usually much better

    De facto the best interactive disassembler and decompiler on the market. Impressive set of APIs, you can write modules or scripts for everything.
  8. OBFUSCATION PROGUARD • Free • Integrated into the build environment

    • NOT Android specific • http://developer.android.com/tools/ help/proguard.html
  9. OBFUSCATION DEXGUARD • Commercial product from ProGuard author. • Android

    specific • Native support to string and code encryption and tamper detection • Very easy to use, with a config file like ProGuard
  10. LOGGING • Remove Logcat logging from your production builds. •

    It can be done with few lines in Proguard and Dexguard, they remove all the calls to Log.d, Log.e etc in the build process • It’s very easy for third party malware or an attacker to access the Logs on Android.
  11. FILE STORAGE EXTERNAL STORAGE • Try to avoid storing your

    data in the shared storage, almost any application can read it. (In 4.4 a small protection at permission level was added android.permission.READ_EXTERNAL _STORAGE, usually users does not check permissions too much anyway… Don’t rely on this.)
  12. FILE STORAGE PRIVATE APP FOLDER • Encrypt your preferences/files •

    With root access they can be modified, avoid store sensitive data at all if possible • With a backup, they can be retrieved from the device usually • The private folder can be found on the device at path /data/data/yourpackage

    Rule: You do NOT implement your own Cryptography
  14. SECURE NETWORK COMMUNICATIONS • It’s your responsibility to protect data

    in transit! • Don’t transmit sensitive information without SSL/TLS • Implement if possibile Certificate Pinning, in this way your communications will be more resistant to MITM attacks, for example if a malicious certificate is pushed into the device, or if an attacker can impersonate your web service with a trusted certificate.
  15. 1PASSWORD READER • Password wallet application for Android, a companion

    application of the Mac/Windows client, to be able to share our passwords between our PC and the mobile device, leveraging Dropbox or the Shared Storage.
  16. RAM MEMORY ATTACKS • An attacker can retrieve and inspect

    the ram memory used by our application and search for sensitive informations. • Avoid storing such sensitive informations inside instance or static variables.
  17. RAM MEMORY ATTACKS • An easiest way to get an

    incomplete (VM only) chunk of live memory from our application is to use the “Dump HPROF” functionality in the monitor tool, with a debuggable application or a device with the flag ro.debuggable=1
  18. RUNTIME MANIPULATION Why modify the code of the application recompiling

    it when we can modify the code at runtime, without alerting the basic tampering detection?
  19. 1PASSWORD READER • Password wallet application for Android, a companion

    application of the Mac/Windows client, to be able to share our passwords between our PC and the mobile device, leveraging Dropbox or the Shared Storage.

    forced for technical limitation in the sharing process between the PC and the device. • Without root permissions, the user can only write in the shared folder, or the application can use third party services, such file sharing API by Dropbox, to share the wallet file.
  21. FIRST LOOK • The 1Password wallet is totally unobfuscated, so

    an attacker can easily understand the logic of the application and the weak points. • First weak spot: LOGS, the application disabled in productions the logging of the user credentials and other internal information to the Logcat, but the logs are only disabled, the code that logs at the critical points (even the user password) it’s in there.
  22. AGIMAT • Simple cheat engine/app for Android using runtime manipulation

    • When more games are supported and if there is interest, it will be open sourced (no time)