How hackerhouse-opensource/rebirth works
Main Components
• Exploit Module – Represent the multipath exploit code (e.g., CVE-2018-4241 directory and associated kernel helpers, kernel_patching, and kernel_helpers files) as a dedicated block. This module is responsible for gaining task-for-pid-zero (tfp0), thereby bypassing AMFI (Apple Mobile File Integrity) and providing root privileges.
• Userland / Lightweight Root Environment – Show the iOS application component (in the “rebirth” directory including the app source files, AppDelegate, and storyboards). This is where the jailbreak payload is installed (non-persistently) to mount the root filesystem writable (on iOS 11.0 – 11.2.6) and to provide a minimal environment for further instrumentation.
• Binpack / System Binaries – Represent the “binpack” directory, which bundles system binaries, libraries, and associated configuration files required to replace or patch system components (including SSH, bash, various shell utilities, etc.). This block supports the modified userland by supplying the necessary executables and native libraries.
• Ancillary Tools – Represent the “tools” directory as several interconnected submodules:
– Debugging and Forensics Utilities (e.g., dumpdecrypted, jtool, and serialsh).
– Networking / Remote Access Utilities (e.g., dropbear SSH integration, netcat).
– Instrumentation and App Hacking Utilities (e.g., Frida support through built libraries and scripts).
– Other helper scripts and binaries (e.g., pincrack, frida-macos-universal).
Relationships and Interactions
• A data/control flow between the core jailbreaking payload, the utilities provided (e.g., dropbear for SSH and other forensic tools) and the external interfaces (like Frida) used in app instrumentation.
Architectural Patterns & Design Principles
• Separation of concerns by clearly differentiating between:
– The kernel-level exploitation and patching components,
– The userland installation that sets up a temporary root environment,
– The bundled binaries (via binpack) that replace standard system tools, and
– The collection of forensic and application-hacking utilities under “tools.”
• That this solution employs “rootless” designs to avoid permanent changes – a design principle worth noting for mobile security practitioners.
Technologies, Frameworks, and Libraries
• iOS/Objective-C for the main jailbreak application (rebirth).
• C (and possibly assembly) for the kernel helpers, multipath exploit (CVE-2018-4241), and various low-level tools.
• QiLin framework components integrated into the jailbreak.
• OS binpack utilities, dropbear (SSH server), Frida (dynamic instrumentation), and dumpdecrypted libraries.
• Xcode environment is used to build the iOS project.