iPhone Rootkit? There's an App for that! - Reverse Engineering Mac ...
iPhone Rootkit? There's an App for that! - Reverse Engineering Mac ... iPhone Rootkit? There's an App for that! - Reverse Engineering Mac ...
Binary Reversing Prep (continued…)6. Dump the decrypted section to a file based on “cryptsize” from step #2 (4096)(gdb) dump memory decrypted.bin 0x2000 (0x2000 + 4096)7. Merge decrypted.bin back into SomeApp using your favorite hex editor.• Relative file offset for the encrypted data will be 0x1000 away from the machheader (aka cryptoff) .8. Don’t forget to disable “cryptid” so that class-dump and other tools will work onour fixed up binary. Change Cryptid to 0.Copyright Trustwave 2010
No More SecretsHint: find the LC_ENCRYPTION_INFO(0x21) load command by converAng “otool –l” output back to 32-‐bit li
- Page 5 and 6: iPhone/iOS Security Overview
- Page 7 and 8: Architecture OverviewApplications P
- Page 9 and 10: Application SecurityCode signing•
- Page 11 and 12: Jailbreaking Overview
- Page 13 and 14: Jailbreakme.com A Thing to Behold
- Page 15 and 16: What it looks likeVisit h'p://jailb
- Page 17 and 18: Weaponizing
- Page 19 and 20: Patch PlanReversing the installui.d
- Page 21 and 22: My “Big Fat Rootkit”… so farC
- Page 23 and 24: Set-upA vanilla un-jailbroken iPhon
- Page 25 and 26: Hardware: Mic and AudioAudio record
- Page 27 and 28: Dumping Process DataSeveral interes
- Page 29 and 30: Targeting iOS ApplicationsiOS isn
- Page 31 and 32: Demo App Backdoor
- Page 33: Binary Reversing Prep (continued…
- Page 37 and 38: Mach Binary Encryption (continued
- Page 39 and 40: What’s your point?For starters…
- Page 41 and 42: Objective-C Method HookingIt’s ca
- Page 43 and 44: Objective-C Method Hook ExampleLets
- Page 45 and 46: Injecting Our LibraryConventionally
- Page 47 and 48: ConclusionsLots of security researc
- Page 49 and 50: Reversing Redux: The Binary “star
- Page 51 and 52: … continued: eggMalformed Times-
- Page 53 and 54: class-dump on installui.dylib (aka
Binary Reversing Prep (continued…)6. Dump the decrypted section to a file based on “cryptsize” from step #2 (4096)(gdb) dump memory decrypted.bin 0x2000 (0x2000 + 4096)7. Merge decrypted.bin back into Some<strong>App</strong> using your favorite hex editor.• Relative file offset <strong>for</strong> the encrypted data will be 0x1000 away from the machheader (aka cryptoff) .8. Don’t <strong>for</strong>get to disable “cryptid” so <strong>that</strong> class-dump <strong>an</strong>d other tools will work onour fixed up binary. Ch<strong>an</strong>ge Cryptid to 0.Copyright Trustwave 2010
Change language