Difference between revisions of "IOS Application Security Testing Cheat Sheet"

Revision as of 15:20, 24 January 2013

DRAFT CHEAT SHEET - WORK IN PROGRESS

Introduction

This cheat sheet provides a checklist of tasks to be performed when testing an iOS application.

When assessing a mobile application several areas should be taken into account: client software, the communication channel and the server side infrastructure.

Testing an iOS application usually requires a jailbroken device. (a device that not pose any restrictions on the software that can be installed on it)

Information gathering

• Observe application behavior (for each role available)
• Does the application request/store/transmit transactions (performs payments)
• Identify access methods and interfaces used
• Identify what frameworks are in use
• Identify server side APIs that are in use
• Identify what protocols are in use
• Identify other applications or services with which the application interacts
• Decrypt Appstore binaries: the apps will be decrypted at runtime by the kernel’s mach loader. Cydia has two applications available: Crackulous and AppCrack. Also, you can use GDB. The “cryptid” field of the LC_ENCRYPTION_INFO identifies if the application is encrypted or not. Use otool –l <app name> | grep –A 4 LC_ENCRYPTION_INFO
• Determine the architecture the application was compiled for: otool –f <app name>
• Get information about what functions, classes and methods are referenced in the application and in the dynamically loaded libraries. Use nm <app name>
• List the dynamic dependencies. Use otool –L <app name>
• Dump the load commands for the application. Use otool –l <app name>
• Dump the runtime information from the compiled application. Identify each class compiled into the program and its associated methods, instance variables and properties. Use class-dump-z <app name>

Determine the security features in place:

• Locate the PIE (Position Independent Executable) - an app compiled without PIE (using the “–fPIE –pie” flag) will load the executable at a fixed address. Check this using the command: otool –hv <app name>
• Stack smashing protection - specify the –fstack-protector-all compiler flag. A “canary” is placed on the stack to protect the saved base pointer, saved instruction pointer and function arguments. It will be verified upon the function return to see if it has been overwritten. Check this using: otool –I –v <app name> | grep stack . If the application was compiled with the stack smashing protection two undefined symbols will be present: “___stack_chk_fail” and “___stack_chk_guard”.
• Identify the use of Automatic Reference Counting (ARC – memory management feature). Set the compiler option “Objective-C Automatic Reference Counting” to “yes”. Check this using: otool –I –v <app name> | grep “_objc_release”. Check for symbols that indicate the presence of ARC: _objc_retainAutoreleaseReturnValue, _objc_autoreleaseReturnValue, _objc_storeStrong, _objc_retain, _objc_release, _objc_retainAutoreleaseReturnValue

Application traffic analysis

• Analyze error messages
• Analyze cacheable information
• Transport layer security (TLS version; NSURLRequest object )
• Attack XML processors
• SQL injection
• Privacy issues (sensitive information disclosure)
• Improper session handling
• Decisions via untrusted inputs
• Broken cryptography
• Unmanaged code
• URL Schemes
• Push notifications
• Authentication
• Authorization
• Session management
• Data storage
• Data validation (input, output)
• Transport Layer protection – are the certificates validated, does the application implement Certificate Pinning
• Denial of service
• Business logic
• UDID usage (privacy concerns)

Runtime analysis

• Disassemble the application (gdb)
• Analyze file system interaction
• Analyze the application with a debugger (gdb): inspecting objects in memory and calling functions and methods; replacing variables and methods at runtime.
• Investigate CFStream and NSStream
• Investigate protocol handlers (application: openURL - validates the source application that instantiated the URL request) for example: try to reconfigure the default landing page for the application using a malicious iframe.
• Buffer overflows and memory corruption
• Client side injection
• Injection using dynamic linker attack

Insecure data storage

• Investigate log files
• Insecure data storage in application folder (var/mobile/Applications), caches, in backups (iTunes)
• Investigate custom created files
• Analyze SQLlite database
• Investigate property list files
• Investigate file caching
• Insecure data storage in keyboard cache
• Investigate Cookies.bynarycookies
• Analyze iOS keychain (/private/var/Keychains/keychain-2.db) – when it is accessible and what information it contains; data stored in the keychain can only be accessible if the attacker has physical access to the device.
• Check for sensitive information in snapshots

Tools

References

• https://www.owasp.org/index.php/Projects/OWASP_Mobile_Security_Project_-_Security_Testing_Guide
• http://pen-testing.sans.org/blog/pen-testing/2011/10/13/mobile-application-assessments-attack-vectors-and-arsenal-inventory#
• http://resources.infosecinstitute.com/iphone-penetration-testing-3/
• Jonathan Zdziarski “Hacking and securing iOS applications” (ch. 6,7,8)
• http://www.mdsec.co.uk/research/iOS_Application_Insecurity_wp_v1.0_final.pdf