Checkra1n Era - Ep 5 - Automating extraction and processing (aka "Merry Xmas!")

By -
After my third post on how to automate an extraction BFU, my great friend, colleague and fellow citizen Giovanni 'sug4r' Rattaro, Tsurugi Linux team leader and core developer, wrote me a message saying: "Belin Mattia! You had a great idea! But we can quickly improve your script!" And I answered: "Yes, why not. How is it going for you in the next couple of weeks? Do you have time?". And Giovanni: "No, I have to deliver the newest version of Tsurugi before Christmas. But still, we can do it!". And I said: "I am also very busy. But yes, we can do it!".

Starting from my original idea, we completely redesigned and organized the script, both in terms of "user interface" (thanks Giovanni for the idea of using ncurses menu!) and functions.

Still, our script is a PoC and must be used just for testing, studying, developing and learning purposes. It is not meant to be a "forensic tool", but we decided in any case to create log files and calculate hashes.

The script has been tested only on Mac OS X, but we plan to test it on Linux and integrate it in Tsurugi Linux in the Mobile Forensics section.

It is opensource and we will be pleased to receive any kind of feedback on how to improve it, add new features or bug fix.

In this post we will explain script's features, basic requirements and we provide instructions on how to use it.

Features

The script has a main menu with 9 options.

Option 1 - Collect device information

This option executes the 'ideviceninfo -s' tool and collects basic information about the connected iOS device (name, model, UDID, iOS version and so on).


The result is stored in two files, in TXT and PLIST format.

Option 2 - Execute live commands

This option executes live commands on the device.
The actual version executes the following commands:
  • date
  • sysctl -a
  • hostname
  • uname -a
  • id
  • df
  • df -ah
  • ifconfig -a
  • netstat -an
  • ltop
  • mount
  • ps -ef
  • ps aux
  • ioreg
It takes about 15 seconds to complete.


The result is stored in a separate TXT file for each executed command.

Option 3 - Execute 'find' commands

This option executes 7 'find' commands to extract relevant file/folder names and specifically:
  • find /private/var/mobile/Library/DataAccess -type d -name "*IMAP-*"
  • find /private/var/mobile/Library/Mail -type f -name "*.pdf" -ls
  • find /private/var/mobile/Library/Mail -type f -name "*.doc*" -ls
  • find /private/var/mobile/Library/Mail -type f -name "*.xls*" -ls
  • find /private/var/mobile/Containers -type d -name "*@s.whatsapp.net*"
  • find /private/var/mobile/Containers -type d -name "*@g.us*"
  • find /private/var -ls
The execution should take about 5 to 10 minutes, depending on the amount of files stored on the device.


The result is stored in a separate TXT file for each executed 'find' command.

Option 4 - Acquire a 'BFU relevant files' image

This option extracts relevant files available BFU and creates a TAR file.
The execution should take about 5 minutes, also when executed AFU.


The result is stored in a TAR file and extracted files are also available in the 'extracted_files' subfolder

Option 5 - Acquire a triage image

This option creates a TAR file of '/private' folder, excluding application Bundles and MobileAsset. 
When in BFU state, the execution should take about 10 to 15 minutes
When in AFU state, the amount of time depends on the total file size and can reach several hours
In our tests the average speed is about 25 GB per hour


The result is stored in a TAR file 

Option 6 - Acquire a full image

This option creates a TAR file of the full file system. 
When in BFU state, the execution should take about 30 minutes
When in AFU state, the amount of time depends on the total file size and can reach several hours
In our tests the average speed is about 25 GB per hour

The result is stored in a TAR file 

Option 7 - Extract and process relevant files

This option extracts relevant files and parse them with Sysdiagnose scripts, Mobile Installation Logs Parser and APOLLO.

This option can be used both BFU or AFU. When BFU not all the files can be extracted, because some of them are available only AFU. The script uses only the available ones and process them.

The execution should take about 5 to 10 minutes.


The result is stored in a separate subfolder fo each executed script.

 

Requirements

The script has some mandatory requirements and some optional requirements.

Mandatory requirements

  • A "checkra1ned" iOS device with and SSH connection on localhost port 22. We didn't test the script with other jailbreaks, but it should work on any device where an SSH connection is available on port 22 and the 'root' user has the default password ('alpine').
  • libimobiledevice
  • sshpass
  • dialog

Optional requirements

Configuration

  • Download the "ios_bfu_triage.sh" script on our GitHub account
  • Save the script in the same folder where you want to store the extractions
  • NOTE: Keep in mind that a full file system acquisition can be quite big. Be sure to have enough space on your disk. The script can also be saved and executed from an external devices.
  • Make the script executable (chomod +x ios_bfu_triage.sh)
  • Download Sysdiagnose scripts, Mobile Installation Logs Parser and APOLLO
  • Extract and stores these scripts in the same folder where you stored the ios_bfu_triage.sh
  • Strictly use the following folder naming schema (see also the following picture)
    • sysdiagnose
    • mib
    • apollo
  • When you know the passcode (aka, you can be in an AFU condition) make sure to keep the phone unlocked by setting "Auto Lock" to never. In this way, options 5, 6 and 7 will be able to extract all the files. In fact, if you are in an AFU condition but the phone is locked at the time of acquisition, all the files in a protection class "ProtectionComplete" cannot be extracted!

Conclusions

Download and test the script!
The generated TAR file (with options 4, 5 and 6) should work once imported in commercial Mobile Forensics tools!

In the meanwhile, Merry Christmas and Happy New Year!!

Comments

Post a Comment

Popular posts from this blog

A first look at Android 14 forensics

By -
Android 14 was released to the public by the Open Handset Alliance on October 4, 2023, and is now available on various smartphones, including the Google Pixel. This blog post aims to explore a list of the majr oartifacts you can find on this version of the Android OS.  For testing and review, I set up a Google Pixel 7A and used it for about a month, with a SIM card and various native and third-party apps installed. The blog post is organized by sections: Device information and general settings User accounts Information on Cellular, Wi-Fi, and Bluetooth connections Native Android applications Google applications Analysis of the use of native and third-party applications Other relevant information As always, I'll try to update this blog post as I test and research. Device information and general settings build.prop TXT format Stored in the root directory of the system partition  Among other things, it contains the device manufacturer, the device model, the operating system ...
Keep reading

Huawei backup decryptor

By -
When doing Mobile Forensics the first and usually the hardest step is to get access to user's data . It depends on the case type, but the so called physical  acquisition is the analyst object of desire. The reason is simple: iOS and Android native backups, respectively adb  and iTunes , contain a subset of user data, because they respect the various apps configurations where they can specify " you can't include me in backups ". Which leads to inconsistent situations like, for example, having WhatsApp data in iTunes backups and not having it in Android adb backups. Not considering WhatsApp, the majority of apps in iOS and Android do not allow their data to be included in backups . In the scenario where  device is unlocked or the lock  code is known (the only scenario considered in this post), the analyst could use the device itself to make the analysis of the installed applications. Anyone who did that at least once knows how uncomfortable is this a...
Keep reading

Dissecting the Android WiFiConfigStore.xml for forensic analysis

By -
Image
A smartphone is often connected to a Wi-Fi network: think of how much time we spend at home, in our office, or even in a public place while studying or exercising. As soon as we can reach a (hopefully trusted) Wi-Fi network, we connect to it! On Android devices, the Wi-Fi connection is managed by the Wi-Fi service. This service must store information about the previously connected Wi-Fi networks so that the phone can reconnect as soon as it's in the vicinity. The file that stores this information is WiFiConfigStore.xml, a simple XML file stored in the Userdata partition under /data/misc/apexdata/com.android.wifi/. The source code describing the contents of this file is  available on the Android source code website . This file is parsed by most commercial and open-source tools. I wanted to go a little more in-depth to take a look at the different Wi-Fi settings. The main XML tag is  <WifiConfigStoreData > . This tag contains the  Version  sub-tag, which contains...
Keep reading