Exclaves -- iOS 18+

Exclaves are Apple’s newest isolated execution environments. Combined with SPTM + TXM, they create the strongest defense-in-depth to date.

Concept

Before Exclaves:
  Security-critical code runs in the kernel (EL1)
  → Kernel compromise = everything lost

Exclaves:
  Security-critical code runs in isolated environments
  → Kernel compromise ≠ access to exclave data
  → Each exclave must be compromised separately

Architecture

┌──────────────────────────────────────┐
│ EL0: Userspace apps                  │
├──────────────────────────────────────┤
│ EL1: XNU Kernel                     │
│   - Reduced trust boundary           │
│   - Cannot access exclave memory     │
├──────────────────────────────────────┤
│ EL2: SPTM + TXM                     │
│   - Page table management            │
│   - Code signing verification        │
├──────────────────────────────────────┤
│ Exclaves:                            │
│   ┌──────────┐ ┌──────────┐         │
│   │ Exclave A│ │ Exclave B│  ...    │
│   │ (crypto) │ │ (biometrc│         │
│   └──────────┘ └──────────┘         │
│   - Isolated memory                  │
│   - Separate code                    │
│   - Minimal interface to kernel      │
├──────────────────────────────────────┤
│ Secure Enclave (SEP)                 │
│   - Keys, biometrics, Secure Boot    │
└──────────────────────────────────────┘

Exclaves vs Secure Enclave

Feature Secure Enclave Exclaves
Hardware Separate processor Same CPU, isolated context
Use case Keys, biometrics, boot Various security-critical tasks
Interface Mailbox (very limited) Structured API
Isolation Physical (separate chip) Logical (SPTM-enforced)
Performance High latency Lower latency

Impact on Exploitation

iOS 18+ exploit chain requirements:
  1. Vulnerability in kernel (EL1) → kernel r/w
  2. SPTM bypass (EL2) → page table control
  3. TXM bypass (EL2) → code signing bypass
  4. Exclave bypass → access to sensitive operations
  5. Possibly: SEP bypass → access to keys

Each step requires a separate vulnerability.
Full chain complexity: extreme.

Current Knowledge

Exclaves are very new (iOS 18, late 2024). Public research is still very limited:

  • Apple has introduced them in the Platform Security Guide
  • Conference presentations are starting to appear (Recon, OffensiveCon, BlackHat)
  • No public exploit or bypass yet

This is the frontier of iOS security research.