iOS Internals and Security Testing
1.0.0
Sebagai sistem Unix yang sesuai, OS X bekerja dengan direktori terkenal yang standar pada semua rasa UNIX:
OS X menambahkan direktori khusus ke pohon unix, di bawah root sistem:
Dari perspektif sistem file, iOS sangat mirip dengan OS X, dengan perbedaan berikut:
File dengan ekstensi .ipa dapat tidak terkompresi dengan mengubah ekstensi menjadi .zip dan unzipping.
/iTunesArtwork
/iTunesArtwork@2x
/iTunesMetadata.plist
/WatchKitSupport/WK
/META-INF
/Payload/
/Payload/<Application>.app/
/Payload/<Application>.app/<Application> ← Apple FairPlay DRM Encrypted Executable
/Payload/<Application>.app/Info.plist A file that contains some of the application specific configurations
/Payload/<Application>.app/_CodeSignature/ Contains a plist file with a signature over all files in the bundle
/Payload/<Application>.app/Assets.car Another zipped archive that contains assets (icons)
/Payload/<Application>.app/Frameworks/ Contains the app native libraries as .dylib or .framework files
/Payload/<Application>.app/PlugIns/ May contain app extensions as .appex files
/Payload/<Application>.app/Core Data It is used to save permanent data for offline use and sync across iCloud devices
/Payload/<Application>.app/PkgInfo An alternate way to specify the type and creator codes of your application or bundle
/Payload/<Application>.app/en.lproj, etc Language packs that contains resources for those specific languages
/var/containers/Bundle/Application/<UUID> Bundle directory; tampering invalidates signature
/var/mobile/Containers/Data/<UUID> Application runtime data
/var/mobile/Containers/Data/<UUID>/Documents/ Contains all the user-generated data
/var/mobile/Containers/Data/<UUID>/Library/ Contains all files that aren't user-specific – caches, preferences, cookies, plist files
/var/mobile/Containers/Data/<UUID>/Library/Caches/
Contains semi-persistent cached files
/var/mobile/Containers/Data/<UUID>/Library/Application Support/
Contains persistent files necessary for running the app
/var/mobile/Containers/Data/<UUID>/Library/Preferences/<bundle id>.plist
Properties that can persist after an application is restarted. Contains NSUserDefaults
/var/mobile/Containers/Data/<UUID>/tmp/ Temporary files that do not need to persist between app launches
File plist adalah file XML terstruktur yang berisi pasangan nilai kunci yang mendukung jenis objek dasar, seperti kamus, daftar, angka dan string. Biasanya objek tingkat atas adalah kamus. Plist dapat menjadi file biner atau XML atau JSON .
| Tipe abstrak | Elemen xml | Kelas Kakao | Jenis Foundation Core |
|---|---|---|---|
| array | <array> | NSArray | CFArray ( CFArrayRef ) |
| kamus | <dict> | NSDictionary | CFDictionary ( CFDictionaryRef ) |
| rangkaian | <string> | NSString | CFString ( CFStringRef ) |
| data | <data> | NSData | CFData ( CFDataRef ) |
| tanggal | <date> | NSDate | CFDate ( CFDateRef ) |
| Nomor - Integer | <integer> | NSNumber ( intValue ) | CFNumber ( CFNumberRef , Nilai Integer) |
| Nomor - Titik Mengambang | <real> | NSNumber ( floatValue ) | CFNumber ( CFNumberRef , nilai poin mengambang) |
| Boolean | <true/> atau <false/> | NSNumber ( boolValue == YES atau boolValue == NO ) | CFBoolean ( CFBooleanRef ; kCFBooleanTrue atau kCFBooleanFalse ) |
Info standar. Plist berisi entri berikut:
plutil -convert xml1 binary_file.plist
plutil -convert xml1 data_file.json -o data_file.plist
https://docs.python.org/3/library/plistlib.html
Aplikasi Pengguna dapat mengakses berjalan sebagai pengguna seluler sementara proses sistem kritis berjalan sebagai root . Namun, kotak pasir memungkinkan kontrol yang lebih baik atas tindakan yang dapat dilakukan oleh proses dan aplikasi.
Misalnya, bahkan jika dua proses dijalankan sebagai pengguna (seluler) yang sama, mereka tidak diizinkan untuk mengakses atau memodifikasi data satu sama lain .
Setiap aplikasi diinstal di bawah /var/mobile/Applications/<UUID> . Uuid acak. Setelah diinstal, aplikasi memiliki akses baca terbatas ke beberapa area dan fungsi sistem (SMS, panggilan telepon ...). Jika suatu aplikasi ingin mengakses kawasan lindung, sembulan yang meminta izin muncul.
Pengembang APP dapat memanfaatkan API Perlindungan Data IOS untuk mengimplementasikan kontrol akses berbutir halus untuk data pengguna yang disimpan dalam memori flash. API dibangun di atas Prosesor Enklave Aman (SEP). SEP adalah coprocessor yang menyediakan operasi kriptografi untuk perlindungan data dan manajemen kunci . Kunci perangkat keras khusus perangkat- perangkat UID (ID unik) -disematkan di kantong aman , memastikan integritas perlindungan data bahkan ketika kernel sistem operasi dikompromikan.
Ketika sebuah file dibuat pada disk, kunci AES 256-bit baru dihasilkan dengan bantuan generator nomor acak berbasis perangkat keras Secure Enclave. Konten file kemudian dienkripsi dengan kunci yang dihasilkan. Dan kemudian, kunci ini disimpan dienkripsi dengan kunci kelas bersama dengan ID kelas, dengan kedua data dienkripsi oleh kunci sistem, di dalam metadata file.
Untuk mendekripsi file, metadata didekripsi menggunakan kunci sistem. Kemudian menggunakan ID kelas, kunci kelas diambil untuk mendekripsi kunci per file dan mendekripsi file.
File dapat ditetapkan ke salah satu dari empat kelas perlindungan yang berbeda, yang dijelaskan secara lebih rinci dalam panduan keamanan iOS.
Setiap aplikasi memiliki direktori home yang unik dan kotak pasir , sehingga mereka tidak dapat mengakses sumber daya sistem yang dilindungi atau file yang disimpan oleh sistem atau oleh aplikasi lain. Pembatasan ini diimplementasikan melalui kebijakan kotak pasir (alias. Profil ), yang ditegakkan oleh kerangka kontrol akses wajib BSD (MAC) tepercaya melalui ekstensi kernel.
Beberapa kemampuan/izin dapat dikonfigurasi oleh pengembang aplikasi (misalnya perlindungan data atau pembagian kunci) dan akan langsung berlaku setelah instalasi. Namun, bagi yang lain, pengguna akan secara eksplisit ditanyai pertama kali aplikasi mencoba mengakses sumber daya yang dilindungi .
String tujuan atau deskripsi penggunaan adalah teks khusus yang ditawarkan kepada pengguna dalam peringatan permintaan izin sistem saat meminta izin untuk mengakses data atau sumber daya yang dilindungi.
Jika memiliki kode sumber asli, Anda dapat memverifikasi izin yang termasuk dalam file Info.plist :
Info.plist di editor default dan cari tombol yang dimulai dengan "Privacy -" . Anda dapat mengganti tampilan untuk menampilkan nilai -nilai mentah dengan mengklik kanan dan memilih "Tampilkan Kunci/Nilai RAW" (cara ini misalnya "Privacy - Location When In Use Usage Description" akan berubah menjadi NSLocationWhenInUseUsageDescription ).
Jika hanya memiliki IPA:
Info.plist terletak di Payload/<appname>.app/Info.plist .plutil -convert xml1 Info.plist ) seperti yang dijelaskan dalam bab "IOS Basic Security Testing", bagian "File Info.plist".UsageDescription : <plist version="1.0">
<dict>
<key>NSLocationWhenInUseUsageDescription</key>
<string>Your location is used to provide turn-by-turn directions to your destination.</string>
Kemampuan perangkat digunakan oleh App Store untuk memastikan bahwa hanya perangkat yang kompatibel yang terdaftar dan karenanya diizinkan untuk mengunduh aplikasi. Mereka ditentukan dalam file Info.plist aplikasi di bawah [UIRequiredDeviceCapabilities](https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/plist/info/UIRequiredDeviceCapabilities)
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>armv7</string>
</array>
Biasanya Anda akan menemukan kemampuan ARMV7, yang berarti bahwa aplikasi ini disusun hanya untuk set instruksi ARMV7, atau jika itu adalah aplikasi universal 32/64-bit.
Misalnya, aplikasi mungkin sepenuhnya bergantung pada NFC untuk bekerja (misalnya aplikasi "NFC Tag Reader"). Menurut referensi kompatibilitas perangkat iOS yang diarsipkan, NFC hanya tersedia mulai dari iPhone 7 (dan iOS 11). Pengembang mungkin ingin mengecualikan semua perangkat yang tidak kompatibel dengan mengatur kemampuan perangkat nfc .
Hak adalah pasangan nilai kunci yang masuk ke aplikasi dan memungkinkan otentikasi di luar faktor runtime, seperti UNIX USER ID. Karena hak ditandatangani secara digital, mereka tidak dapat diubah. Hak digunakan secara luas oleh aplikasi sistem dan daemon untuk melakukan operasi istimewa spesifik yang seharusnya membutuhkan proses untuk berjalan sebagai root. Ini sangat mengurangi potensi eskalasi hak istimewa dengan aplikasi atau daemon sistem yang dikompromikan.
Misalnya, jika Anda ingin mengatur kemampuan "perlindungan data default", Anda harus pergi ke tab kemampuan di Xcode dan mengaktifkan perlindungan data . Ini langsung ditulis oleh Xcode ke file <appname>.entitlements sebagai hak com.apple.developer.default-data-protection dengan nilai default NSFileProtectionComplete . Di IPA kita mungkin menemukan ini di embedded.mobileprovision sebagai:
<key>Entitlements</key>
<dict>
...
<key>com.apple.developer.default-data-protection</key>
<string>NSFileProtectionComplete</string>
</dict>
Untuk kemampuan lain seperti HealthKit, pengguna harus diminta izin, oleh karena itu tidak cukup untuk menambahkan hak, kunci khusus, dan string harus ditambahkan ke file Info.plist aplikasi.
Secure Enclave adalah bagian dari A7 dan SOC baru yang digunakan untuk perlindungan data, ID sentuh, dan ID wajah. Tujuan dari kantong yang aman adalah untuk menangani kunci dan info lainnya seperti biometrik yang cukup sensitif untuk tidak ditangani oleh prosesor aplikasi. Ini diisolasi dengan filter perangkat keras sehingga AP tidak dapat mengaksesnya. Ini berbagi RAM dengan AP, tetapi bagian RAM - TZ0 dienkripsi. Secure Enclave sendiri adalah inti prosesor AKF 4MB yang dapat diklamur yang disebut Prosesor Enclave Secure (SEP). Teknologi yang digunakan mirip dengan TrustZone/Securcore ARM tetapi berisi kode hak milik untuk inti Apple KF secara umum dan SEP secara khusus.
SOC di setiap perangkat memiliki coprocessor AES dengan kunci GID dan kunci UID .
ID Unik Perangkat (UID) dan ID Grup Perangkat (GID) adalah AES 256-bit kunci menyatu (UID) atau dikompilasi (GID) ke dalam prosesor aplikasi selama pembuatan. Tidak ada perangkat lunak atau firmware yang dapat membacanya secara langsung; Mereka hanya dapat melihat hasil operasi enkripsi atau dekripsi yang dilakukan dengan menggunakannya. UID unik untuk setiap perangkat dan tidak direkam oleh Apple atau pemasoknya. GID adalah umum untuk semua prosesor di kelas perangkat dan digunakan sebagai tingkat perlindungan tambahan saat memberikan perangkat lunak sistem selama instalasi dan pemulihan. Mengintegrasikan kunci -kunci ini ke dalam silikon membantu mencegah mereka dirusak atau dilewati, atau diakses di luar mesin AES.
Kunci GID ( Kunci ID Grup ) adalah kunci AES 256-bit yang dibagikan oleh semua perangkat dengan prosesor aplikasi yang sama. Kunci GID adalah bagian dari bagaimana iOS mengenkripsi perangkat lunak pada perangkat. Ini adalah salah satu komponen dari sistem keamanan iOS, yang juga termasuk tanda tangan SHSH. Kunci ini berbeda pada setiap model SOC Apple.
Kunci GID sejauh ini belum diekstraksi dari perangkat apa pun, jadi satu -satunya cara untuk menggunakannya adalah dengan melewati mesin AES itu sendiri.
Tetapi
GID dapat diperoleh melalui prosedur serangan booting dingin yang mahal (https://en.m.wikipedia.org/wiki/cold_boot_attack) dan prosedur pemindaian soC dengan litografi/lekrografer/lithography/litk. Eksperimen seperti itu tidak adil mahal dan kompleks, jadi tidak pernah terpikir oleh siapa pun untuk mencoba mengimplementasikannya kecuali untuk Cellebrite laboratorium swasta. Cellebrite tidak berbagi penelitiannya.
Kunci UID ( kunci ID unik perangkat ) adalah kunci perangkat keras AES 256-bit, unik untuk setiap iPhone.
Beberapa tombol turunan dihitung oleh layanan kernel IOAESACCELATOR di boot. Kunci -kunci ini dihasilkan dengan enkripsi nilai statis baik dengan kunci UID (pengidentifikasi 0x7d0) atau kunci GID (pengidentifikasi 0x3e8).
Key 0x835 -Dihasilkan dengan Enkripsi 0x01010101010101010101010101010101 dengan UID-Key. Digunakan untuk perlindungan data.
Key 0x836 -Dihasilkan dengan Mengenkripsi 0x00E5A0E6526FAE66C5C1C6D4F16D6180 dengan UID-Key. Ini dihitung oleh kernel selama pemulihan, tetapi dimusnahkan selama boot normal. Ini juga dihitung oleh bootloader yang aman, dan satu -satunya penggunaan yang diketahui adalah mendekripsi LLB di NOR. Seperti 0x835 , berbeda untuk setiap perangkat.
Kunci 0x837 - Dihasilkan dengan enkripsi 0x345A2D6C5050D058780DA431F0710E15 dengan kunci GID S5L8900, menghasilkan 0x188458A6D15034DFE386F23B61D43774 . Ini digunakan sebagai kunci enkripsi untuk file IMG2. Dengan diperkenalkannya IMG3 di iPhone OS 2.0, KBAG sekarang digunakan sebagai pengganti kunci 0x837 . Karena iPhone OS versi 1.x hanya digunakan pada iPhone dan iPod Touch (keduanya menggunakan S5L8900) nilai terenkripsi untuk prosesor lain tidak penting.
Key 0x838 -Dihasilkan dengan mengenkripsi 0x8C8318A27D7F030717D2B8FC5514F8E1 dengan uid-key. Kunci berbasis UID-AES lain, digunakan untuk mengenkripsi semuanya kecuali LLB di NOR (iBoot, Devicetree, gambar).
Key 0x899 -Dihasilkan dengan mengenkripsi 0xD1E8FCB53937BF8DEFC74CD1D0F1D4B0 dengan UID-Key. Penggunaan tidak diketahui.
Key 0x89a -Dihasilkan dengan mengenkripsi 0xDB1F5B33606C5F1C1934AA66589C0661 dengan UID-Key, mendapatkan kunci khusus perangkat. Digunakan pada perangkat A4. Ini digunakan untuk mengenkripsi gumpalan shsh pada perangkat.
Key 0x89b -Dihasilkan dengan Enkripsi 0x183E99676BB03C546FA468F51C0CBD49 dengan UID-Key. Ini digunakan untuk mengenkripsi kunci partisi data.
Key 0x8A3 -Dihasilkan dengan Enkripsi 0x568241656551e0cdf56ff84cc11a79ef dengan UID-Key (menggunakan AES-256-CBC). Ini digunakan selama peningkatan perangkat lunak pada A12 dan yang lebih baru untuk mengenkripsi nilai "generator" (menggunakan AES-128-CBC) sebelum mendapatkannya menjadi nonce.
Info lebih lanjut: https://css.csail.mit.edu/6.858/2020/readings/ios-security-may19.pdf
https://www.securitylab.ru/contest/428454.php
https://www.securitylab.ru/contest/429973.php
File modul Objective-C memiliki ekstensi ".m" (jika campuran C ++ dan Objective-C digunakan, ekstensi ".mm"). File header - “.h”. Semua objek kelas yang dibuat di Objective-C harus dialokasikan dalam tumpukan. Oleh karena itu, tipe ID, yang merupakan penunjuk ke objek kelas mana pun (pada kenyataannya, batal *), memperoleh signifikansi khusus. Pointer nol disebut sebagai nol konstan. Dengan demikian, pointer ke kelas mana pun dapat dilemparkan ke tipe ID. Muncul masalah: Bagaimana cara mengetahui kelas mana objek yang bersembunyi di bawah ID milik? Ini dilakukan berkat invarian ISA, yang hadir dalam objek kelas apa pun yang mewarisi NSObject kelas basis khusus (awalan NS adalah singkatan dari Langkah Berikutnya). Isa invarian adalah kelas tipe yang dipesan. Objek jenis ini memungkinkan Anda untuk mengetahui namanya sendiri dan kelas dasar, satu set invarian kelas, serta prototipe dari semua metode yang telah diimplementasikan oleh objek ini dan alamatnya (melalui daftar penyeleksi lokal). Semua kata-kata yang dicadangkan Objective-C selain dari C yang dicadangkan, dimulai dengan simbol @(misalnya @protocol, @selector, @interface). Biasanya, nama -nama invarian kelas cakupan (@private, @protected) dimulai dengan garis bawah. Untuk string, kakao memiliki kelas NSString yang sangat berguna. Konstanta string dari kelas ini ditulis sebagai @"Hello World", dan bukan sebagai C String Constant "Hello World" yang biasa. Jenis bool (pada dasarnya char yang tidak ditandatangani) dapat mengambil nilai konstan ya dan tidak. Semua kata-kata cadangan khusus objektif-C (yang berbeda dari bahasa C dan ditemukan dalam file header objc/objc.h) tercantum di bawah ini:
@interface mulai mendeklarasikan kelas atau kategori (kategori adalah ekstensi kelas tanpa warisan)
@end melengkapi deklarasi definisi kelas, kategori atau protokol apa pun
@private membatasi ruang lingkup invarian kelas dengan metode kelas (mirip dengan C ++)
@protected secara default. Membatasi ruang lingkup invarian kelas untuk metode kelas dan metode kelas turunan (mirip dengan C ++)
@public menghapus pembatasan pelingkupan (mirip dengan C ++)
@try mendefinisikan blok dengan kemungkinan lemparan pengecualian (mirip dengan C ++)
@throw melempar objek pengecualian (mirip dengan C ++)
@catch() menangani pengecualian yang dilemparkan di blok @try sebelumnya (mirip dengan C ++)
@finally secara mendefinisikan blok setelah blok @try yang dikontrol dilewati terlepas dari apakah pengecualian dilemparkan atau tidak
@class bentuk disingkat deklarasi kelas (hanya nama (mirip dengan c ++))
@selector(method_name) Mengembalikan pemilih yang dikompilasi untuk metode metode method_name
@protocol(protocol_name) Mengembalikan contoh kelas protokol bernama protocol_name
@encode(type_spec) menginisialisasi string karakter yang akan digunakan untuk mengenkripsi data tipe type_spec
@synchronized() mendefinisikan blok kode yang dieksekusi hanya dengan satu utas pada titik waktu tertentu
@implementation mulai mendefinisikan kelas atau kategori
@protocol memulai deklarasi protokol (analog dengan kelas C ++ yang terdiri dari fungsi virtual murni)
Untuk memaksa objek untuk menjalankan metode, Anda perlu mengirimkannya pesan yang sama dengan metode yang diperlukan. Pesan ini disebut pemilih metode. Sintaks untuk pengiriman adalah sebagai berikut:
[receiver method];
- (void) addObject: (id) otherObject;
Jika Anda menempatkan tanda plus + pada awal prototipe metode, maka metode tersebut akan dianggap sebagai metode kelas dan, secara alami, tidak akan menerima parameter diri implisit (ini mirip dengan menyatakan metode statis dalam C ++). Dan tanpa invarian ISA dari objek yang ditunjukkan oleh diri sendiri, pointer super, tentu saja, juga tidak akan berhasil. Dengan demikian, prototipe metode apa pun dinyatakan seperti ini:
- | + (<return type>) mainMethodNamePart
[: (<type of first parameter>) nameOfFirstFormalParameter
[[optionalMethodNamePart]: (<type of second parameter>) secondFormalParameterName] ...
]
Misalnya:
+ (Class)class;
+ (id)alloc;
- (id)init;
- (void)addObject: (id)anObject;
+ (NSString *)stringWithCString: (const char*)aCString usingUncoding: (enum NSStringEncoding)encoding;
- (NSString *)initStringWithFormat: (NSString *)format, ...;
Dokumentasi Pengembang Apple
https://developer.apple.com/library/archive/documentation/macosx/conceptual/osx_technology_overview/systemframeworks/systemframeworks.html
https://www.theiphonewiki.com/wiki//system/library/frameworks
Kerangka kerja disimpan di beberapa lokasi pada sistem file:
Selain itu, aplikasi dapat mencakup kerangka kerja mereka sendiri.
Dokumentasi Pengembang Apple - Jaringan
Dokumentasi Pengembang Apple - Networkextension
Dokumentasi Pengembang Apple - NetworkingDriverKit
Sebagian besar aplikasi yang mungkin Anda temui terhubung ke titik akhir jarak jauh. Bahkan sebelum Anda melakukan analisis dinamis apa pun (misalnya penangkapan dan analisis lalu lintas), Anda dapat memperoleh beberapa input awal atau titik masuk dengan menyebutkan domain yang seharusnya dikomunikasikan oleh aplikasi tersebut.
Biasanya domain ini akan hadir sebagai string dalam biner aplikasi. Seseorang dapat mengekstrak domain dengan mengambil string dengan rabin2 -zz <path_to_binary> atau di Ida Pro. Opsi yang terakhir memiliki keuntungan yang jelas: dapat memberi Anda konteks, karena Anda dapat melihat dalam konteks mana setiap domain digunakan dengan memeriksa referensi silang.
Dari sini Anda dapat menggunakan informasi ini untuk memperoleh lebih banyak wawasan yang mungkin digunakan nanti selama analisis Anda, misalnya Anda dapat mencocokkan domain dengan sertifikat yang disematkan atau melakukan pengintaian lebih lanjut pada nama domain untuk mengetahui lebih banyak tentang lingkungan target.
Implementasi dan verifikasi koneksi yang aman dapat menjadi proses yang rumit dan ada banyak aspek yang perlu dipertimbangkan. Misalnya, banyak aplikasi menggunakan protokol lain selain dari HTTP seperti XMPP atau paket TCP biasa, atau melakukan pinning sertifikat dalam upaya untuk mencegah serangan MITM.
Kerangka kerja jaringan diperkenalkan di Apple Worldwide Developers Conference (WWDC) pada tahun 2018 dan merupakan pengganti Sockets API. Kerangka kerja jaringan tingkat rendah ini menyediakan kelas untuk mengirim dan menerima data dengan jaringan yang dinamis, keamanan dan dukungan kinerja.
TLS 1.3 diaktifkan secara default dalam kerangka jaringan, jika argumen using: .tls digunakan. Ini adalah opsi yang disukai daripada kerangka transportasi aman Legacy.
URLSession dibangun di atas kerangka kerja jaringan dan menggunakan layanan transportasi yang sama. Kelas juga menggunakan TLS 1.3 secara default, jika titik akhir adalah https.
URLSession harus digunakan untuk koneksi HTTP dan HTTPS, alih -alih menggunakan kerangka kerja jaringan secara langsung. Kelas secara asli mendukung kedua skema URL dan dioptimalkan untuk koneksi tersebut. Dibutuhkan lebih sedikit kode boilerplate, mengurangi kecenderungan kesalahan dan memastikan koneksi yang aman secara default. Kerangka kerja jaringan hanya boleh digunakan ketika ada persyaratan jaringan tingkat rendah dan/atau lanjutan.
Dokumentasi Apple resmi mencakup contoh menggunakan Kerangka Jaringan untuk mengimplementasikan NetCAT dan URLSession untuk mengambil data situs web ke dalam memori.
https://developer.limneos.net/
https://www.theiphonewiki.com/wiki//system/library/privateframeworks
Alat terbaru untuk perangkat Anda dapat ditemukan di sini https://canijailbreak.com
Penelitian ini pada dasarnya ditulis untuk iPhone 5s 5s melalui X dengan iOS 10-15 dan dapat diperbarui dalam jangka panjang jika alat bootrom pwnage baru akan dirilis. Lihat https://www.theiphonewiki.com/wiki/bootrom#bootrom_exploits
https://repo.chariz.com misalnya)killall SpringBoardBuka file .deb/.ipa dengan file manager filza dan tekan install, jika Anda melihat kesalahan dengan instalasi .deb Coba temukan dan instal semua dependensi
Instal AppSync Unified dari https://cydia.akemi.ai/ repo
https://apt.bingner.com/
https://apt.thebigboss.org/repofiles/cydia/
https://cydia.saurik.com
https://repo.dynastic.co/
https://getdelta.co/
https://cokepokes.github.io/
https://cydia.akemi.ai/
https://nscake.github.io/
https://repo.chariz.com/
https://mrepo.org/
https://rejail.ru/
https://repo.hackyouriphone.org/
https://build.frida.re/ - Frida
https://cydia.radare.org/ - radare2
Instal di desktop
brew install libimobiledevice ideviceinstaller libirecovery
sudo port install idevicerestore
idevice_id List attached devices or print device name of given device idevicebackup Create or restore backup for devices (legacy) idevicebackup2 Create or restore backups for devices running iOS 4 or later idevicecrashreport Retrieve crash reports from a device idevicedebug Interact with the debugserver service of a device idevicedebugserverproxy Proxy a debugserver connection from a device for remote debugging idevicediagnostics Interact with the diagnostics interface of a device ideviceenterrecovery Make a device enter recovery mode ideviceimagemounter Mount disk images on the device ideviceinfo Show information about a connected device idevicename Display or set the device name idevicepair Manage host pairings with devices and usbmuxd idevicescreenshot Gets a screenshot from the connected device idevicesetlocation Simulasi lokasi di perangkat idevicesyslog relay syslog dari perangkat yang terhubung
ideviceinstaller --list-apps
ideviceinstaller --install <Application.ipa>
ideviceinstaller --uninstall <bundle id>
idevicedebug -d run <bundle id>
irecovery --shell memungkinkan komunikasi dengan iBoot/IBSS dari perangkat iOS
idevicerestore --latest mengembalikan firmware baru ke perangkat idevicerestore --erase --latest
Memaksa memulihkan dengan menghapus semua data
utilitas inetcat untuk mengekspos koneksi mentah ke perangkat iproxy 2222:22 mengikat port lokal 2222 dan maju ke 22 perangkat USB pertama
Instal pada Conduit File Apple Perangkat "2"
Gunakan Imazing atau Ifunbox untuk mengakses sistem file
Instal Filza File Manager
Instal OpenSsh di perangkat dan jalankan di desktop:
iproxy 2222:22
ssh -p 2222 root@localhost
Kata sandi IOS default untuk root adalah alpine . Jangan ubah jika Anda memiliki ingatan yang buruk
Instal pada perangkat Newterm 2 dari https://repo.chariz.com untuk menggunakan terminal lokal
cd /private/var/containers/Bundle/Application/<guid>/myapp.app
// Contains compiled code, statically linked files, compressed NIB files.
cd /private/var/mobile/Containers/Data/Application/
ls -lrt // Your freshly installed IPA is at the bottom of list
cd [app guid]/Documents/
cd [app guid]/Library/
/private/var/Keychains
TrustStore.sqlite3
keychain-2.db
pinningrules.sqlite3
// Extract IPA (whether App Store encrypted or not)
scp -r -P 2222 root@localhost:/var/containers/Bundle/Application/<app GUID>/hitme.app ~/hitme.app
// Different to SSH, the uppercase P for Port with SCP. Order important.
scp -P 2222 root@localhost:/var/root/overflow.c localfilename.c
// from Jailbroken device to local machine
// Caution:no space after the root@localhost: Otherwise you copy the entire filesystem!
scp -P 2222 root@localhost:/private/var/mobile/Containers/Data/Application/<App GUID>/Library/Caches/Snapshots/com.my.app
// from local machine to remote Jailbroken device
scp -P 2222 hello.txt root@localhost:/var/root/
Instal libflex dan melenturkan dari https://nscake.github.io/
Buka Newterm dan Run killall SpringBoard
Sekarang Anda dapat memuat fleksibel di dalam aplikasi apa pun dengan Longpress di StatusBar
Frida adalah toolkit instrumentasi biner dinamis yang memungkinkan kita untuk menjalankan skrip dalam perangkat lunak yang sebelumnya terkunci. Singkatnya, Frida memungkinkan Anda menyuntikkan potongan JavaScript ke aplikasi asli di Windows, Mac, Linux, iOS dan Android.
Tambahkan Frida Repo ke Cydia - https://build.frida.re/
Jika Anda tidak memiliki Python 3:
brew install pyenv
pyenv install 3.9.0 (atau yang terbaru tersedia)
Lalu instal
pip3 install frida-tools
Daftar frida-ls-devices Daftar Perangkat Tersedia
frida-ps -U Daftar Semua Nama Proses Berjalan dan PID pada perangkat USB
Daftar frida-ps -Uai Semua aplikasi yang diinstal pada perangkat USB
frida-ps -Ua daftar semua aplikasi yang sedang berjalan di perangkat USB
Daftar frida-ls-devices Semua perangkat terlampir
frida-ps -D 0216027d1d6d3a03 Hubungkan Frida ke perangkat tertentu
Alat frida-discover untuk menemukan fungsi internal dalam suatu proses
frida-trace -U Twitter -i "*URL*" Menelusuri API Asli
frida-trace -U -f com.toyopagroup.picaboo -I "libcommonCrypto*"
Luncurkan panggilan aplikasi dan lacak crypto crypto
frida-trace -U Twitter -m "-[NSURL* *HTTP*]" Menelusuri Objective-C API
frida -U -n Twitter -l inject.js suntikan skrip ke dalam proses pada perangkat USB melalui repl
frida -n cat terhubung ke kucing dengan nama
frida -f foobar force terbuka foobar
frida -U -f foobar --no-pause terbuka foobar di atas USB dan Force Start. Mulai aplikasi berjalan
frida-ps -U | grep -i myapp mendapatkan ID proses aplikasi target dari perangkat yang terhubung USB
frida -U -f foobar --no-pause -q --eval 'console.log("Hi Frida");'
Jalankan skrip dan berhenti Frida
Pada titik ini kami memiliki NativeFunction kami yang disimpan dalam variabel play_sound . Sebut saja seperti fungsi reguler play_sound() dan juga ingat untuk memberikan parameter input ( int ): play_sound(1007)
Menyatukan semuanya:
var address = Module.findExportByName('AudioToolbox', 'AudioServicesPlaySystemSound')
var play_sound = new NativeFunction(address, 'void', ['int'])
play_sound(1007)
Anda harus mendapatkan contoh objek terlebih dahulu, baik:
var instance = ObjC.classes.ClassName.alloc().init();ObjC.choose , like - if you know there's only one instance already created somewhere on the heap - you can to something like var instance = ObjC.chooseSync(ObjC.classes.ClassName)[0];var instance = ObjC.classes.MySingleton.getInstance().myInterestingInstance();and then call the method on the instance:
instance.setSomething();
or, if the method signature takes an argument, like - setSomething: , you can also pass the argument (just remember to put a _ instead of ObjC's : ):
instance.setSomething_(argument);
frida -U "My App" // Attach Frida to app over USB
Process.id
419
Process.getCurrentThreadId()
3843
var b = "hello frida"
console.log(b)
"hello frida"
c = Memory.allocUtf8String(b)
"0x1067ec510"
Memory.readUtf8String(c)
"hello frida"
console.log(c)
0x1067ec510
console.log(c.readUtf8String(5))
hello
console.log(c.readUtf8String(11))
hello frida
ptrToC = new NativePointer(c);
"0x1067ec510"
console.log(ptrToC)
0x1067ec510
console.log(ptrToC.readCString(8))
hello fr
Memory.readUtf8String(ptrToC)
"hello frida"
Objective-C's syntax includes the : and @ characters. These characters were not used in the Frida Javascript API .
// Attach to playground process ID
frida -p $(ps -ax | grep -i -m1 playground |awk '{print $1}')
ObjC.available
true
ObjC.classes.UIDevice.currentDevice().systemVersion().toString()
"11.1"
ObjC.classes.NSBundle.mainBundle().executablePath().UTF8String()
ObjC.classes.UIWindow.keyWindow().toString()
RET: <WKNavigation: 0x106e165c0>
// shows Static Methods and Instance Methods
ObjC.classes.NSString.$ownMethods
ObjC.classes.NSString.$ivars
var myDate = ObjC.classes.NSDate.alloc().init()
console.log(myDate)
2019-04-19 19:03:46 +0000
myDate.timeIntervalSince1970()
1555700626.021566
myDate.description().toString()
"2019-04-19 19:03:46 +0000"
var a = ObjC.classes.NSUUID.alloc().init()
console.log(a)
4645BFD2-94EE-413D-9CE5-8982D41ED6AE
a.UUIDString()
{
"handle": "0x7ff3b2403b20"
}
a.UUIDString().toString()
"4645BFD2-94EE-413D-9CE5-8982D41ED6AE"
var b = ObjC.classes.NSString.stringWithString_("foo");
b.isKindOfClass_(ObjC.classes.NSString)
true
b.isKindOfClass_(ObjC.classes.NSUUID)
false
b.isEqualToString_("foo")
true
b.description().toString()
"foo"
var c = ObjC.classes.NSString.stringWithFormat_('foo ' + 'bar ' + 'lives');
console.log(c)
foo bar lives
var url = ObjC.classes.NSURL.URLWithString_('www.foobar.com')
console.log(url)
www.foobar.com
url.isKindOfClass_(ObjC.classes.NSURL)
true
console.log(url.$class)
NSURL
var b = ObjC.classes.NSString.stringWithString_("foo");
var d = ObjC.classes.NSData
d = b.dataUsingEncoding_(1) // NSASCIIStringEncoding = 1, NSUTF8StringEncoding = 4,
console.log(d)
<666f6f> // This prints the Hex value "666f6f = foo"
d.$className
"NSConcreteMutableData"
var x = d.CKHexString() // Get you the Byte array as a Hex string
console.log(x)
666f6f
x.$className
"NSTaggedPointerString"
var newStr = ObjC.classes.NSString.stringWithUTF8String_[d.bytes]
// demoapp is the iOS app name
myapp=$(ps x | grep -i -m1 demoapp | awk '{print $1}')
frida-trace -i "getfsent*" -p $myapp
// Connect to process with Frida script
frida --codeshare mrmacete/objc-method-observer -p 85974
Process.enumerateModules()
// this will print all loaded Modules
Process.findModuleByName("libboringssl.dylib")
{
"base": "0x1861e2000",
"name": "libboringssl.dylib",
"path": "/usr/lib/libboringssl.dylib",
"size": 712704
}
Process.findModuleByAddress("0x1c1c4645c")
{
"base": "0x1c1c2a000",
"name": "libsystem_kernel.dylib",
"path": "/usr/lib/system/libsystem_kernel.dylib",
"size": 200704
}
DebugSymbol.fromAddress(Module.findExportByName(null, 'strstr'))
{
"address": "0x183cb81e8",
"fileName": "",
"lineNumber": 0,
"moduleName": "libsystem_c.dylib",
"name": "strstr"
}
Module.findExportByName(null, 'strstr')
"0x183cb81e8"
Module.getExportByName(null,'strstr')
"0x183cb81e8"
Process.findModuleByAddress("0x183cb81e8")
{
"base": "0x183cb6000",
"name": "libsystem_c.dylib",
"path": "/usr/lib/system/libsystem_c.dylib",
"size": 516096
}
a = Process.findModuleByName("Reachability")
a.enumerateExports()
....
{
"address": "0x102fab020",
"name": "ReachabilityVersionString",
"type": "variable"
},
{
"address": "0x102fab058",
"name": "ReachabilityVersionNumber",
"type": "variable"
}
....
...
..
frida -U -f funky-chicken.debugger-challenge --no-pause -q --eval 'var x={};Process.enumerateModulesSync().forEach(function(m){x[m.name] = Module.enumerateExportsSync(m.name)});' | grep -B 1 -A 1 task_threads
"address": "0x1c1c4645c",
"name": "task_threads",
"type": "function"
frida -U -f funky-chicken.debugger-challenge --no-pause -q --eval 'var x={};Process.findModuleByAddress("0x1c1c4645c");'
{
"base": "0x1c1c2a000",
"name": "libsystem_kernel.dylib",
"path": "/usr/lib/system/libsystem_kernel.dylib",
"size": 200704
}
[objc_playground]-> var a = ObjC.classes.NSString.stringWithString_("foo");
[objc_playground]-> a.superclass().toString()
"NSString"
[objc_playground]-> a.class().toString()
"NSTaggedPointerString"
// PASTE THIS CODE INTO THE FRIDA INTERFACE...
Interceptor.attach(ObjC.classes.NSTaggedPointerString['- isEqualToString:'].implementation, {
onEnter: function (args) {
var str = new ObjC.Object(ptr(args[2])).toString()
console.log('[+] Hooked NSTaggedPointerString[- isEqualToString:] ->' , str);
}
});
// TRIGGER YOUR INTERCEPTOR
[objc_playground_2]-> a.isEqualToString_("foo")
[+] Hooked NSTaggedPointerString[- isEqualToString:] -> foo
1 // TRUE
[objc_playground_2]-> a.isEqualToString_("bar")
[+] Hooked NSTaggedPointerString[- isEqualToString:] -> bar
0 // FALSE
// frida -U -l open.js --no-pause -f com.yd.demoapp
// the below javascript code is the contents of open.js
var targetFunction = Module.findExportByName("libsystem_kernel.dylib", "open");
Interceptor.attach(targetFunction, {
onEnter: function (args) {
const path = Memory.readUtf8String(this.context.x0);
console.log("[+] " + path)
}
});
frida-trace --v Check it works frida-trace --help Excellent place to read about Flags frida-trace -f objc_playground Spawn and NO trace frida-trace -m "+[NSUUID UUID]" -U "Debug CrackMe" Trace ObjC UUID static Class Method frida-trace -m "*[ComVendorDebugger* *]" -U -f com.robot.demo.app ObjC wildcard trace on Classes frida-trace -m "*[YDDummyApp.UserProfileMngr *]" -U -f com.robot.demo.app Trace mangled Swift functions frida-trace -i "getaddrinfo" -i "SSLSetSessionOption" -U -f com.robot.demo Trace C function on iOS frida-trace -m "*[*URLProtection* *]" -U -f com.robot.demo For https challenge information frida-trace -m "*[NSURLSession* *didReceiveChallenge*]" -U -f com.robot.demo Check whether https check delegate used frida-trace -U -f com.robot.demo.app -I libsystem_c.dylib Trace entire Module. frida-trace -p $myapp -I UIKit Trace UIKit Module. frida-trace -f objc_playground -I CoreFoundation Trace CoreFoundation Module. frida-trace -I YDRustyKit -U -f com.yd.mobile Trace my own module. frida-trace -m "-[NSURLRequest initWithURL:]" -U -f com.robot.demo Get app files and APIs frida-trace -m "-[NSURL initWithString:]" -U -f com.robot.demo Find the API endpoints frida-trace -m "*[NSURL absoluteString]" -U -f com.robot.demo My favorite of these
frida-trace -i "*strcpy" -f hitme aaaa bbbb
Instrumenting functions...
_platform_strcpy: Loaded handler at "/.../__handlers__/libSystem.B.dylib/_platform_strcpy.js"
Started tracing 1 function. Press Ctrl+C to stop.
Edit the auto-generated, template Javascript file.
-----------
onEnter: function (log, args, state) {
// strcpy() arg1 is the Source. arg0 is the Destination.
console.log('n[+] _platform_strcpy()');
var src_ptr = args[1].toString()
var src_string = Memory.readCString(args[1]);
var src_byte_array = Memory.readByteArray(args[1],4);
var textDecoder = new TextDecoder("utf-8");
var decoded = textDecoder.decode(src_byte_array);
console.log('[+] src_ptrt-> ' , src_ptr);
console.log('[+] src_stringt-> ' + src_string);
console.log('[+] src_byte_arrayt-> ' + src_byte_array);
console.log('[+] src_byte_array sizet-> ' + src_byte_array.byteLength);
console.log('[+] src_byte_array decodedt-> ' + decoded);
},
Hasilnya:
[+] _platform_strcpy()
[+] src_ptr -> 0x7ffeefbffaa6
[+] src_string -> aaaa
[+] src_byte_array -> [object ArrayBuffer]
[+] src_byte_array size -> 4
[+] decoded -> aaaa
[+] _platform_strcpy()
[+] src_ptr -> 0x7ffeefbffaab
[+] src_string -> bbbb
[+] src_byte_array -> [object ArrayBuffer]
[+] src_byte_array size -> 4
[+] decoded -> bbbb
frida-ps -Uai // get your bundle ID
frida --codeshare mrmacete/objc-method-observer -U -f funky-chicken.push-demo
[+] At the Frida prompt...
observeSomething('*[ABC* *]'); // any Class beginning with ABC, regardless of instance or static class
observeSomething('-[WKWebsiteDataStore httpCookieStore]');
observeSomething('-[WKWebAllowDenyPolicyListener *]');
observeSomething('-[WKWebView loadRequest:]'); // dump the URL to hit
observeSomething('-[WKWebView load*]'); // you get all HTML, js, css, etc
observeSomething('-[WKWebView loadHTMLString:baseURL:]') // really effective; see the entire request
observeSomething('-[WKWebView *Agent]'); // try to see if somebody set a custom UserAgent
observeSomething('*[* isEqualToString*]'); // watch string compares
bash -c "exec -a YDFooBar ./frida-server &"
frida-server -l 0.0.0.0:19999 &
frida-ps -ai -H 192.168.0.38:19999
frida-trace -m "*[NSURLSession* *didReceiveChallenge*]" -H 192.168.0.38:19999 -f com.youdog.rusty.tinyDormant
Objection is a runtime mobile exploration toolkit powered by Frida to assess the security posture of mobile applications without needing to write scripts .
pip3 install objection
objection device_type Get information about an attached device
objection explore Start the objection exploration REPL
objection explore --startup-command 'ios jailbreak simulate'
objection explore --startup-command 'ios jailbreak disable'
Early Instrumentation
ls
env This will print out the locations of the applications Library, Caches and Documents directories
!<shell command> Run OS command
file download <remote path> [<local path>]
file upload <local path> [<remote path>]
Upload/Download
file cat <file> View file
memory dump all <local destination> memory dump from_base <base_address> <size_to_dump> <local_destination>
Dump all memory/Dump part
memory list modules List loaded modules in memory
memory list exports <module_name> Exports of a loaded module
memory search "<pattern eg: 41 41 41 ?? 41>" (--string) (--offsets-only)
memory write "<address>" "<pattern eg: 41 41 41 41>" (--string)
Search/Write
sqlite connect pewpew.sqlite Query the sqlite database
sqlite execute schema Have a look at the table structure
sqlite execute query select * from data;
Execute any query
import <local path frida-script> Import frida script
jobs list List running scripts/jobs
jobs kill <job id> Kill script/job
ios plist cat credentials.plist Read plist file
ios info binary Inspect binary info
ios sslpinning disable --quiet Disable SSL pinning
ios jailbreak simulate Simulate a jailbroken environment to understand how an application behaves
ios jailbreak disable Jailbreak detection bypass
ios nsuserdefaults get Dump NSUserDefaults
ios nsurlcredentialstorage dump Dump NSURLCredentialStorage
ios keychain dump Dump app keychain
ios cookies get Get secure flags and sensitive data stored in cookies
ios monitor crypto monitor Hooks CommonCrypto to output information about cryptographic operation
ios ui dump Dump UI hierarchy
ios ui alert "<message>" Show alert
env Local app paths
ios bundles list_bundles List bundles of the application
ios bundles list_frameworks List external frameworks used by the application
ios hooking list classes List classes of the app
ios hooking search classes <str> Search a class that contains a string
ios hooking list class_methods List methods of a specific class
ios hooking search methods <str> Search a method that contains a string
ios hooking watch class <class_name>
Hook all the methods of a class, dump all the initial parameters and returns
ios hooking watch method "-[<class_name> <method_name>]" --dump-args --dump-return --dump-backtrace
Hook an specific method of a class dumping the parameters, backtraces and returns
ios hooking set return_value "-[<class_name> <method_name>]" false
This will make the selected method return the indicated boolean
ios hooking generate simple <class_name>
Generate hooking template.
r2 frida://device-id/Snapchat Attach to a running app using the display name.
r2 frida://attach/usb//Gadget Attach to the Frida Gadget
r2 frida://device-id//com.snapchat.android Spawn an app using two // and the package name.
r2 frida://spawn/usb/device-id/com.android.app Or explicitly using the word spawn
r2 frida://spawn/usb//com.android.app Or without entering the device-id
=!? Get the list of commands
=!?~^i :
i Show target information
ii[*] List imports
il List libraries
is[*] <lib> List symbols of lib (local and global ones)
iE[*] <lib> Same as is, but only for the export global ones
iEa[*] (<lib>) <sym> Show address of export symbol
isa[*] (<lib>) <sym> Show address of symbol
ic <class> List Objective-C classes or methods of <class>
ip <protocol> List Objective-C protocols or methods of <protocol>
=!i Shows target information
=!i* Shows target information in r2 form
.=!i* Radare2 imports all the dynamic binary data from Frida. Eg: which architecture, endianness, pointer size, etc...
.=!iE* Radare2 imports all the dynamic export data from Frida for all the dynamic libraries.
.=!iE* <lib> Radare2 imports all the dynamic export data from Frida for only one specific library.
.=!ii* Radare2 imports all the dynamic import data from Frida.
=!ii <lib> List imports. Commonly used with the symbol ~ , which is the internal grep of r2 .
=!ii* <lib> List imports in r2 form.
=!il List libraries. Commonly used with the symbol ~ , which is the internal grep of r2.
=!iE <lib> List exports of library(ies)
=!iEa (<lib>) <sym> Show address of export symbol
=!iEa* (<lib>) <sym> Show address of export symbol in r2 format
=!isa[*] (<lib>) <sym> Show address of symbol
=!ic List classes
=!/ keyword Search hex/string pattern in memory ranges (see search.in=?)
> =!?~^/ :
/[x][j] <string|hexpairs> Search hex/string pattern in memory ranges (see search.in=?)
/w[j] string Search wide string
/v[1248][j] value Search for a value honoring e cfg.bigendian of given width
> =!?~^d :
db (<addr>|<sym>) List or place breakpoint
db- (<addr>|<sym>)|* Remove breakpoint(s)
dc Continue breakpoints or resume a spawned process
dd[-][fd] ([newfd]) List, dup2 or close filedescriptors
dm[.|j|*] Show memory regions
dma <size> Allocate bytes on the heap, address is returned
dmas <string> Allocate a string inited with on the heap
dmad <addr> <size> Allocate bytes on the heap, copy contents from
dmal List live heap allocations created with dma[s]
dma- (<addr>...) Kill the allocations at (or all of them without param)
dmp <addr> <size> <perms> Change page at
dmm List all named squashed mapsdmh List all heap allocated chunksdmhj List all heap allocated chunks in JSONdmh* Export heap chunks and regions as r2 flagsdmhm Show which maps are used to allocate heap chunksdp Show current piddpt Show threadsdr Show thread registers (see dpt)dl libname Dlopen a librarydl2 libname [main] Inject library using Frida's >= 8.2 new APIdt (<addr>|<sym>) ... Trace list of addresses or symbolsdth (<addr>|<sym>) (x y..) Define function header (z=str,i=int,v=hex barray,s=barray)dt- Clear all tracingdtr <addr> (<regs>...) Trace register valuesdtf <addr> [fmt] Trace address with format (^ixzO) (see dtf?)dtSf[*j] [sym|addr] Trace address or symbol using the stalker (Frida >= 10.3.13)dtS[*j] seconds Trace all threads for given seconds using the stalkerdi[0,1,-1] [addr] Intercept and replace return value of addressdx [hexpairs] Inject code and execute it (TODO)dxc [sym|addr] [args..] Call the target symbol with given args e[?] [a[=b]] List/get/set config evaluable vars
[0x00000000] > = ! e
e patch.code=true
e search.in=perm:r--
e search.quiet=false
e stalker.event=compile
e stalker.timeout=300
e stalker.in=raw =!. script.js
=!ic List iOS classes
More info: https://mobile-security.gitbook.io/mobile-security-testing-guide/ios-testing-guide/0x06c-reverse-engineering-and-tampering#tampering-and-runtime-instrumentation
Frida GUI.
Frida GUI.
Frida GUI. https://github.com/FuzzySecurity/Fermion
More info:
https://frida.re/docs/examples/ios/
https://frida.re/docs/frida-trace/
https://frida.re/docs/examples/ios/
https://github.com/sensepost/objection/wiki/Using-objection
Apple's Entitlements Troubleshooting – https://developer.apple.com/library/content/technotes/tn2415/_index.html
Apple's Code Signing – https://developer.apple.com/support/code-signing/
Cycript Manual – http://www.cycript.org/manual/
Frida iOS Tutorial – https://www.frida.re/docs/ios/
Frida iOS Examples – https://www.frida.re/docs/examples/ios/
r2frida Wiki – https://github.com/enovella/r2frida-wiki/blob/master/README.md
Charlie Miller, Dino Dai Zovi. The iOS Hacker's Handbook. Wiley, 2012 – https://www.wiley.com/en-us/iOS+Hacker's+Handbook-p-9781118204122
Jonathan Levin. Mac OS X and iOS Internals: To the Apple's Core. Wiley, 2013 – http://newosxbook.com/MOXiI.pdf
Install SSL Kill Switch 2 from https://github.com/nabla-c0d3/ssl-kill-switch2/releases/
Open your settings and enable SSL Kill Switch 2
Run Charles on PC.
Install Charles Root Certificate on iOS device:
Help → SSL Proxing → Install Charles Root Certificate on Mobile Device or Remote Browser.
The following window will appear:
Depending on your network architecture the IP address Charles is running on may differ.
Proxy → SSL Proxying Settings... → Add (Include) → Host: * ; Pelabuhan: *
Since all binary files inside an .ipa are encrypted with AES and being decrypted with a private key by Secure Enclave Processor at the runtime there is a few ways to decrypt it:
If you don't have Node.js:
brew install nvm
nvm install node
To dump decrypted ipa using bagbak utility install it on desktop:
sudo npm install -g bagbak
Then download your application from the App Store and dump:
bagbak <bundle id or name> --uuid <uuid> --output <output>
There are several ways to run the hardware AES engine:
Patch iBoot to jump to aes_crypto_cmd
Use OpenIBoot
Use XPwn with a kernel patch
Use Greenpois0n console:
ideviceenterrecovery
irecovery --shell
go aes dec <file>
Use ipwndfu
Use checkra1n
Run checkra1n with -p to run into pongoOS (https://github.com/checkra1n/pongoOS) and use the aes command over USB
If you want to disassemble an application from the App Store, remove the FairPlay DRM first.
After decrypting .ipa file open app binary in disassembler like IDA Pro .
In this section the term "app binary" refers to the Macho-O file in the application bundle which contains the compiled code, and should not be confused with the application bundle - the IPA file.
If you have a license for IDA Pro, you can analyze the app binary using IDA Pro as well.
To get started, simply open the app binary in IDA Pro.
Upon opening the file, IDA Pro will perform auto-analysis, which can take a while depending on the size of the binary. Once the auto-analysis is completed you can browse the disassembly in the IDA View (Disassembly) window and explore functions in the Functions window, both shown in the screenshot below.
https://github.com/ChiChou/IDA-ObjCExplorer/blob/master/ObjCExplore.py – Obj-C Classes Explorer for IDA Pro. Just press Ctrl + Shift + E .
https://github.com/avast/retdec-idaplugin – RetDec decompiler for IDA Pro. Just press Ctrl + D .
https://github.com/zynamics/objc-helper-plugin-ida – zynamics Objective-C helper script.
https://github.com/techbliss/Frida_For_Ida_Pro – Connect frida.
https://github.com/vadimszzz/idapython/blob/master/cortex_m_firmware.py – IDA Python module for loading ARM Cortex M firmware.
https://github.com/saelo/ida_scripts/blob/master/kernelcache.py – Identify and rename function stubs in an iOS kernelcache.
https://github.com/luismiras/IDA-iOS-scripts/blob/master/find_iOS_syscalls.py – Find iOS syscalls.
https://github.com/stefanesser/IDA-IOS-Toolkit/blob/master/listAllKEXT.py – List all Kexts.
https://github.com/stefanesser/IDA-IOS-Toolkit/blob/master/findSyscallTable.py – This script searches the iOS syscall table within the iOS kernelcache.
https://github.com/stefanesser/IDA-IOS-Toolkit/blob/master/fixupSysctlSet.py – This script ensures that all sysctl_oid structures referenced by the sysctl_set segment are marked correctly.
https://github.com/bazad/ida_kernelcache – An IDA Toolkit for analyzing iOS kernelcaches.
You can use class-dump to get information about methods in the application's source code.
Note the architectures: armv7 (which is 32-bit) and arm64 . This design of a fat binary allows an application to be deployed on all devices. To analyze the application with class-dump, we must create a so-called thin binary, which contains one architecture only:
iOS8-jailbreak:~ root# lipo -thin armv7 DamnVulnerableIOSApp -output DVIA32
And then we can proceed to performing class-dump:
iOS8-jailbreak: ~ root# class-dump DVIA32
@interface FlurryUtil : ./DVIA/DVIA/DamnVulnerableIOSApp/DamnVulnerableIOSApp/YapDatabase/Extensions/Views/Internal/
{
}
+ (BOOL)appIsCracked ;
+ (BOOL)deviceIsJailbroken ; Note the plus sign, which means that this is a class method that returns a BOOL type. A minus sign would mean that this is an instance method. Refer to later sections to understand the practical difference between these.
Strings are always a good starting point while analyzing a binary, as they provide context to the associated code. For instance, an error log string such as "Cryptogram generation failed" gives us a hint that the adjoining code might be responsible for the generation of a cryptogram.
In order to extract strings from an iOS binary, you can use GUI tools such as Ghidra or Cutter or rely on CLI-based tools such as the strings Unix utility strings <path_to_binary> or radare2's rabin2 rabin2 -zz <path_to_binary> . When using the CLI-based ones you can take advantage of other tools such as grep (eg in conjunction with regular expressions) to further filter and analyze the results.
nm
nm libprogressbar.a | less
rabin2
rabin2 -s file
radare2
is~FUNC
Check URLs:
strings <binary inside app bundle> | grep -E 'session|https'
strings <binary inside app bundle> | grep -E 'pinning'
rabin2 -qz <binary inside app bundle> // in Data Section
rabin2 -qzz <binary inside app bundle> // ALL strings in binary
jtool -dA __TEXT.__cstring c_playground
Dumping C-Strings from address 0x100000f7c (Segment: __TEXT.__cstring)..
Address : 0x100000f7c = Offset 0xf7c
0x100000f7c: and we have a winner @ %ldr
0x100000f98: and that's a wrap folks!r
IDA Pro can be used for obtaining cross references by right clicking the desired function and selecting Show xrefs .
w0 = 32-bitx0 = 64-bitwzr or xzr . Write to = discard, read from = 0 .sp - unlike other instruction sets, never modified implicitly (eg no push / pop ).pc , not modifiable directly.str ).mov to copy one register to another, eg mov x0, x1 -> x0 = x1 .0 loaded from wzr / xzr .orr x0, xzr, 5 .movz + movk , eg: movz x0 , 0x1234 , lsl 32
movk x0 , 0x5678 , lsl 16
movk x0 , 0x9abcx0 = 0x123456789abc .movn for negative values, eg movn x0, 1 -> x0 = -1 .lsl and lsr instructions = logic-shift-left and logic-shift-right, eg lsl x0, x0, 8 -> x0 <<= 8 .lsl and lsr not only used as instructions, but also as operands to other instructions (see movz above).asl for arithmetic shift also exists, but less frequently used.ldr and str with multiple variations and addressing modes:ldr x0, [x1] -> x0 = *x1str x0, [x1] -> *x1 = x0ldr x0, [x1, 0x10] -> x0 = *(x1 + 0x10)ldp / stp to load/store two registers at once behind each other, eg:stp x0, x1, [x2] -> *x2 = x0; *(x2 + 8) = x1;xN for 64-bit, wN for 32-bitldrh / srth for 16-bitldrb / strb for 8-bitldrsw x0, [x1] -> load 32-bit int, sign extend to 64-bitldrsh x0, [x1] -> load 16-bit int, sign extend to 64-bitldrsb x0, [x1] -> load 8-bit int, sign extend to 64-bitstr instructions)ldr x0, [x1, 0x10]ldr x0, [x1, 0x10]! (notice the ! ) -> x1 += 0x10; x0 = *x1;ldr x0, [x1], 0x10 -> x0 = *x1; x1 += 0x10;adr x0, 0x12345 (only works for small offset from PC)adrp + add : adrp x0 , 0xffffff8012345000 ; "address of page", last 12 bits are always zero
add x0 , x0 , 0x678ldr .Note: Only dealing with integral types here. The rules change when floating-point is involved.
x0 - x7 first 8 arguments, rest on the stack (low address to high) with natural alignment (as if they were members of a struct)x8 pointer to where to write the return value if >128 bits, otherwise scratch registerx9 - x17 scratch registersx18 platform register (reserved, periodically zeroed by XNU)x19 - x28 callee-savedx29 frame pointer (basically also just callee-saved)x30 return addressx19 - x28 usually start like this: stp x24 , x23 , [ sp , - 0x40 ] !
stp x22 , x21 , [ sp , 0x10 ]
stp x20 , x19 , [ sp , 0x20 ]
stp x29 , x30 , [ sp , 0x30 ]
add x29 , sp , 0x30 ldp x29 , x30 , [ sp , 0x30 ]
ldp x20 , x19 , [ sp , 0x20 ]
ldp x22 , x21 , [ sp , 0x10 ]
ldp x24 , x23 , [ sp ], 0x40
retadd sp, sp, 0x... and sub sp, sp, 0x... .x0 - x7 come before variadic arguments on the stack, naturally aligned.x0 .x0 , the second/upper half in x1 .x8 to where the result is written.nzcv holds condition flags (Negative, Zero, Carry, oVerflow).instr.cond ), others as source operands ( instr ..., cond ). List of condition codes:eq / ne = equal/not equallt / le / gt / ge = less than/less or equal/greater than/greater or equal (signed)lo / ls / hi / hs = lower/lower or same/higher/higher or same (unsigned)cs / cc = carry set/carry clear are aliases of hs / lo .cmp = most common/basic compare instruction, sets condition flags. Examples: cmp x0 , x1
cmp x0 , 3cmn = compare negativetst = bitwise testadds / adcs = add/add with carrysubs / sbcs = subtract/subtract with carrynegs / ngcs = negate/negate with carrycset = conditional set, eg: cmp x0 , 3
cset x0 , lox0 = (x0 < 3)csel = conditional select, eg: cmp x0 , 3
csel x0 , x1 , x2 , lox0 = (x0 < 3) ? x1 : x2ccmp = conditional compare, eg: cmp x0 , 3
ccmp x0 , 7 , 2 , hs
b.hi 0xffffff8012345678hi condition will be true if x0 < 3 || x0 > 7 (third ccmp operand is raw nzcv data).b = simple branch, jump to PC-relative address. b 0xffffff8012345678 cmp x0 , 3
b.lo 0xffffff8012345678 ; jump to 0xffffff8012345678 if x < 3cbz / cbnz = compare-branch-zero and compare-branch-non-zero. cmp xN , 0
b.eq 0x... cmp xN , 0
b.ne 0x...if(x) or if(!x) .)tbz / tbnz = test single bit and branch if zero/non-zero.tbz x0, 3, ... translates to if((x0 & (1 << 3)) == 0) goto ... .bl = branch-and-link (eg bl 0xffffff8012345678 )x30 and jump to PC-relative address. Used for static function calls.blr = branch-and-link to register (eg blr x8 )x30 and jump to address in x8 . Used for calls with function pointers or C++ virtual methods.br = branch to register (eg br x8 )x8 . Used for tail calls.ret = return to address in register, default: x30x30 (eg ret x8 ), but compiler doesn't usually generate that.nop = do nothingsvc = make a system call using an immediate value (eg svc 0x80 ). Note that the immediate value is separate from the syscall number. XNU ignores the immediate and expects the syscall number in x16 .. = special symbol that refers to the address of the instruction it is used in (eg adr x0, . )Install the following prerequisites:
brew install ldid xz
Set up the THEOS environment variable:
echo "export THEOS=~/theos" >> ~/.zshrc
source ~/.zshrc
Clone Theos:
git clone --recursive https://github.com/theos/theos.git $THEOS
Get the toolchain:
Xcode contains the toolchain.
Get an iOS SDK:
Xcode always provides the latest iOS SDK, but as of Xcode 7.3, it no longer includes private frameworks you can link against. This may be an issue when developing tweaks. You can get patched SDKs from our SDKs repo.
curl -LO https://github.com/theos/sdks/archive/master.zip
TMP=$(mktemp -d)
unzip master.zip -d $TMP
mv $TMP/sdks-master/*.sdk $THEOS/sdks
rm -r master.zip $TMP
Logos is a Perl regex-based preprocessor that simplifies the boilerplate code needed to create hooks for Objective-C methods and C functions with an elegant Objective-C-like syntax. It's most commonly used along with the Theos build system, which was originally developed to create jailbreak tweaks. Logos was once integrated in the same Git repo as Theos, but now has been decoupled from Theos to its own repo.
Logos aims to provide an interface for Cydia Substrate by default, but can be configured to directly use the Objective-C runtime.
Logos is a component of the Theos development suite.
%hookf(return type, functionName, arguments list...) {
/* body */
}
Generate a function hook for the function named functionName . Set functionName in %init to an expression if the symbol should be dynamically looked up.
Contoh:
// Given the function prototype (only add it yourself if it's not declared in an included/imported header)
FILE *fopen(const char *path, const char *mode);
// The hook is thus made
%hookf(FILE *, fopen, const char *path, const char *mode) {
puts("Hey, we're hooking fopen to deny relative paths!");
if (path[0] != '/') {
return NULL;
}
return %orig; // Call the original implementation of this function
}
// functions can also be looked up at runtime, if, for example, the function is in a private framework
%hookf(BOOL, MGGetBoolAnswer, CFStringRef string) {
if (CFEqual(string, CFSTR("StarkCapability"))) {
return YES;
}
return %orig;
}
%ctor() {
%init(MGGetBoolAnswer = MSFindSymbol(NULL, "_MGGetBoolAnswer"));
}
%ctor {
/* body */
}
Generate an anonymous constructor (of default priority). This function is executed after the binary is loaded into memory. argc , argv , and envp are implicit arguments so they can be used as they would be in a main function.
%dtor {
/* body */
}
Generate an anonymous deconstructor (of default priority). This function is executed before the binary is unloaded from memory. argc , argv , and envp are implicit arguments so they can be used as they would be in a main function.
The directives in this category open a block of code which must be closed by an %end directive (shown below). These should not exist within functions or methods.
%group GroupName
/* %hooks */
%end
Generate a hook group with the name GroupName . Groups can be used for conditional initialization or code organization. All ungrouped hooks are in the default group, initializable via %init without arguments.
Cannot be inside another %group block.
Grouping can be used to manage backwards compatibility with older code.
Contoh:
%group iOS8
%hook IOS8_SPECIFIC_CLASS
// your code here
%end // end hook
%end // end group ios8
%group iOS9
%hook IOS9_SPECIFIC_CLASS
// your code here
%end // end hook
%end // end group ios9
%ctor {
if (kCFCoreFoundationVersionNumber > 1200) {
%init(iOS9);
} else {
%init(iOS8);
}
}
%hook ClassName
/* objc methods */
%end
Open a hook block for the class named ClassName .
Can be inside a %group block.
Contoh:
%hook SBApplicationController
- (void)uninstallApplication:(SBApplication *)application {
NSLog(@"Hey, we're hooking uninstallApplication:!");
%orig; // Call the original implementation of this method
}
%end
%new
/* objc method */
%new(signature)
/* objc method */
Add a new method to a hooked class or subclass by adding this directive above the method definition. signature is the Objective-C type encoding for the new method; if it is omitted, one will be generated.
Must be inside a %hook or %subclass block.
Contoh:
%new
- (void)handleTapGesture:(UITapGestureRecognizer *)gestureRecognizer {
NSLog(@"Recieved tap: %@", gestureRecognizer);
}
%subclass ClassName: Superclass <Protocol list>
/* %properties and methods */
%end
Generate a subclass at runtime. Like @property in normal Objective-C classes, you can use %property to add properties to the subclass. The %new specifier is needed for a method that doesn't exist in the superclass. To instantiate an object of the new class, you can use the %c operator.
Can be inside a %group block.
Contoh:
// An interface is required to be able to call methods of the runtime subclass using block syntax.
@interface MyObject : NSObject
@property (nonatomic, retain) NSString * someValue;
@end
%subclass MyObject : NSObject
%property (nonatomic, retain) NSString * someValue;
- (instancetype)init {
if ((self = %orig)) {
[self setSomeValue:@"value"];
}
return self;
}
%end
%ctor {
// The runtime subclass cannot be linked at compile time so you have to use %c().
MyObject *myObject = [[%c(MyObject) alloc] init];
NSLog(@"myObject: %@", [myObject someValue]);
}
%property (nonatomic|assign|retain|copy|weak|strong|getter=...|setter=...) Type name;
Add a property to a %subclass just like you would with @property to a normal Objective-C subclass as well as adding new properties to existing classes within %hook.
Must be inside a %hook or %subclass block.
%end
Close a %group, %hook or %subclass block.
The directives in this category should only exist within a function or method body.
%init;
%init([<ClassName>=<expr>, …]);
%init(GroupName[, [+|-]<ClassName>=<expr>, …]);
Initialize a group's method and function hooks. Passing no group name will initialize the default group. Passing ClassName=expr arguments will substitute the given expressions for those classes at initialization time. The + sigil (as in class methods in Objective-C) can be prepended to the classname to substitute an expression for the metaclass. If not specified, the sigil defaults to - , to substitute the class itself. If not specified, the metaclass is derived from the class.
The class name replacement is specially useful for classes that contain characters that can't be used as the class name token for the %hook directive, such as spaces and dots.
Contoh:
%hook ClassName
- (id)init {
return %orig;
}
%end
%ctor {
%init(ClassName=objc_getClass("SwiftApp.ClassName"));
}
%c([+|-]ClassName)
Evaluates to ClassName at runtime. If the + sigil is specified, it evaluates to MetaClass instead of Class. If not specified, the sigil defaults to - , evaluating to Class.
%orig
%orig(args, …)
Call the original hooked function or method. Doesn't work in a %new'd method. Works in subclasses, strangely enough, because MobileSubstrate will generate a super-call closure at hook time. (If the hooked method doesn't exist in the class we're hooking, it creates a stub that just calls the superclass implementation.) args is passed to the original function - don't include self and _cmd , Logos does this for you.
Contoh:
%hook ClassName
- (int)add:(int)a to:(int)b {
if (a != 0) {
// Return original result if `a` is not 0
return %orig;
}
// Otherwise, use 1 as `a`
return %orig(1, b);
}
%end
&%orig
Get a pointer to the original function or method. Return type is void (*)(id, SEL[, arg types])
Contoh:
// Call from outside hooked method:
void (*orig_ClassName_start)(id, SEL) = nil;
void doStuff(id self, SEL _cmd) {
if (self && orig_ClassName_start) {
orig_ClassName_start(self, _cmd);
}
}
%hook ClassName
- (void)start {
%orig;
orig_ClassName_start = &%orig;
dispatch_after(dispatch_time(DISPATCH_TIME_NOW, 1 * NSEC_PER_SEC),
dispatch_get_main_queue(), ^{
doStuff(self, _cmd);
});
}
%end
// Call with another object:
%hook ClassName
- (int)add:(int)a to:(int)b {
int (*_orig)(id, SEL, int, int) = &%orig;
ClassName * myObject = [ClassName new];
int r = _orig(myObject, _cmd, 1, 2);
[myObject release];
return r;
}
%end
Real world example at PreferenceLoader
%log;
%log([(<type>)<expr>, …]);
Dump the method arguments to syslog. Typed arguments included in %log will be logged as well.
You can use logify.pl to create a Logos source file from a header file that will log all of the functions of that header file. Here is an example of a very simple Logos tweak generated by logify.pl.
Given a header file named SSDownloadAsset.h :
@interface SSDownloadAsset : NSObject
- (NSString *)finalizedPath;
- (NSString *)downloadPath;
- (NSString *)downloadFileName;
+ (id)assetWithURL:(id)url type:(int)type;
- (id)initWithURLRequest:(id)urlrequest type:(int)type;
- (id)initWithURLRequest:(id)urlrequest;
- (id)_initWithDownloadMetadata:(id)downloadMetadata type:(id)type;
@end
You can find logify.pl at $THEOS/bin/logify.pl and you would use it as so:
$THEOS/bin/logify.pl ./SSDownloadAsset.h
The resulting output should be:
%hook SSDownloadAsset
- (NSString *)finalizedPath { %log; NSString * r = %orig; NSLog(@" = %@", r); return r; }
- (NSString *)downloadPath { %log; NSString * r = %orig; NSLog(@" = %@", r); return r; }
- (NSString *)downloadFileName { %log; NSString * r = %orig; NSLog(@" = %@", r); return r; }
+ (id)assetWithURL:(id)url type:(int)type { %log; id r = %orig; NSLog(@" = %@", r); return r; }
- (id)initWithURLRequest:(id)urlrequest type:(int)type { %log; id r = %orig; NSLog(@" = %@", r); return r; }
- (id)initWithURLRequest:(id)urlrequest { %log; id r = %orig; NSLog(@" = %@", r); return r; }
- (id)_initWithDownloadMetadata:(id)downloadMetadata type:(id)type { %log; id r = %orig; NSLog(@" = %@", r); return r; }
%end
| Perpanjangan | Process order |
|---|---|
| X | will be processed by Logos, then preprocessed and compiled as Objective-C. |
| xm | will be processed by Logos, then preprocessed and compiled as Objective-C++. |
| xi | will be preprocessed first, then Logos will process the result, and then it will be compiled as Objective-C. |
| xmi | will be preprocessed first, then Logos will process the result, and then it will be compiled as Objective-C++. |
xi or xmi files enable Logos directives to be used in preprocessor macros, such as #define . You can also import other Logos source files with the #include statement. However, this is discouraged, since this leads to longer build times recompiling code that hasn't changed. Separating into x and xm files, sharing variables and functions via extern declarations, is recommended.
These file extensions control how a build system such as Theos should build a Logos file. Logos itself does not take the file extension into account and works regardless of whether a file is Objective-C or Objective-C++.
https://theos.dev/docs/
https://cydia.saurik.com/faq/developing.html
http://www.cydiasubstrate.com/id/7cee77bc-c4a5-4b8b-b6ef-36e7dd039692/
http://www.cydiasubstrate.com/inject/
https://iphonedev.wiki/index.php/Cydia_Substrate
https://cwcaude.github.io/project/tutorial/2020/07/02/iOS-tweak-dev-1.html
https://cwcaude.github.io/project/tutorial/2020/07/04/iOS-tweak-dev-2.html
https://cwcaude.github.io/project/tutorial/2020/07/12/iOS-tweak-dev-3.html
https://cwcaude.github.io/project/tutorial/2020/07/16/iOS-tweak-dev-4.html
