IBoot

iBoot is the stage 2 bootloader for all Apple products. It replaces the old bootloader, BootX. Compared with its predecessor, iBoot improves authentication performed in the boot chain.

For x86-based Macs, the boot process starts by running code stored in secured UEFI Boot ROM (stage 1). Boot ROM has two primary responsibilities: to initialize system hardware and to select an operating system to run (the POST and UEFI component). For ARM-based Macs, the Boot ROM does not include UEFI.

For iPhones, iPads and ARM-based Macs, the boot process starts by running the device's Boot ROM. The Boot ROM loads the Low-Level Bootloader (LLB), which is the stage 1 bootloader and loads iBoot. If all goes well, iBoot will then proceed to load the iOS, iPadOS or macOS kernel as well as the rest of the operating system. If the iBoot fails to load or fails to verify iOS, iPadOS or macOS, the bootloader jumps to DFU ( D evice F irmware U pdate) mode; otherwise it loads the remaining kernel modules. Since Apple A7 and Apple M1, the LLB is stored on NAND flash of iPhone or iPad, or SSD of Apple Silicon Mac.

On x86 Macs, iBoot is located in. Once the kernel and all drivers necessary for booting are loaded, the boot loader starts the kernel’s initialization procedure. At this point, enough drivers are loaded for the kernel to find the root device.

Memory safety
Apple has modified the C compiler toolchain that is used to build iBoot in order to advance memory safety since iOS 14. This advancement is designed to mitigate entire classes of common memory corruption vulnerabilities such as buffer overflows, heap exploitations, type confusion vulnerabilities, and use-after-free attacks. These modifications can potentially prevent attackers from successfully escalating their privileges to run malicious code, such as an attack involving arbitrary code execution.

Source code leak incident
in 2018, a portion of iBoot source code for iOS 9 was leaked on GitHub, Apple then issued a copyright takedown request (DMCA) to GitHub to remove the repository. It was believed an Apple employee was responsible for the leak. However, this was not confirmed by Apple.